8 Using the CellCLI Utility

This chapter describes the Cell Control Command-Line Interface (CellCLI) utility for managing Oracle Exadata Storage Server Software. CellCLI provides many of the features that are provided with SQL*Plus, including the use of script files. This chapter contains the following topics:

Related Topics

8.1 Overview of the CellCLI Utility

The CellCLI utility is the command-line administration tool for Oracle Exadata Storage Server Software. CellCLI runs on each cell to enable you to manage an individual cell. You use CellCLI to start and stop the cell, to manage cell configuration information, to enable or disable cells, and to manage objects in the cell environment. The command-line utility is already installed when Oracle Exadata Storage Server is shipped. This section contains the following topics:

8.1.1 Starting CellCLI

You can start CellCLI from the operating system command line on the cell that you want to manage or remotely from a network-attached client using Secure Shell (SSH). The command-line syntax is as follows:

cellcli [port_number] [-n] [-m] [-xml] [-v | -vv | -vvv] [-x] [-e command]

The port_number in the preceding command specifies the HTTP port number of the Management Server (MS) for the cell. If the port_number argument is omitted, then the CellCLI utility uses the value assigned to the HTTP_PORT variable in the cellinit.ora file on the cell. If the HTTP_PORT variable in the cellinit.ora file is not set, then the port number defaults to 8888.

The following table lists the options that can be used with the CellCLI command:

Option Description

-n

Runs the CellCLI utility in noninteractive mode. This option suppresses the command prompt and disables the command-line editing features.

-m

Runs CellCLI monitor (read-only) mode.

-xml

Causes output to be displayed in XML format for the Oracle Enterprise Manager.

-v, -vv, and -vvv

Sets the log level. The -v option is for fine, -vv is for finer, and -vvv is for the finest level.

-x

Suppresses the banner.

-e command

Runs the specified CellCLI command. CellCLI exits after running the command. For example:

$ cellcli -e list cell detail
$ cellcli -e "list celldisk attributes name where name   -
  like '.*cell01'"

CellCLI does not have a login parameter or a connect command. CellCLI uses the cell operating system authentication. The directory from which CellCLI is invoked is the default directory for unqualified file access in CellCLI SPOOL and START commands.

When starting CellCLI, a banner is displayed showing the cell efficiency ratio. Cell efficiency ratio is the ratio between data accessed by the storage cell and data processed by the database for the cell. Larger values mean more offloading to the cell. The cell efficiency ratio is the same as the value displayed for the offloadEfficiency attribute in the CellCLI LIST CELL command.

Related Topics

8.1.2 Understanding Command Syntax and Options for CellCLI

CellCLI syntax is as follows:

{admin-command | object-command object} [options] ;

In the preceding syntax, the following arguments are used:

  • admin-command is an administrative action.

  • object-command is an action performed on an object.

  • object is an object or target on which a command performs an action.

  • options extend the use of a command combination to include additional parameters for the command.

When using the CellCLI utility, the following rules apply:

  • Commands, objects, and options are not case-sensitive except where explicitly stated, such as in string patterns used in filtering strings with the LIKE operator.

  • Use single quotation marks or double quotation marks around the name of an object that includes spaces or punctuation. The use of quotation marks should match. For example, "this is incorrect' is incorrect because the first mark is double quotation marks, and the second is a single quotation mark.

  • The current, local cell is the cell to which all CellCLI commands apply.

  • A semicolon (;) is optional at the end of a CellCLI command.

  • A hyphen (-) is used at the end of a line to continue a long command onto the next line.

8.1.3 Reserved Words

The following are CellCLI reserved words:

ABORT
ACTIVE
ACTIVEREQUEST
ALERTDEFINITION
ALERTHISTORY
ALL
ALTER
ASSIGN
BBU
BMC
CALIBRATE
CATPLAN
CELL
CONFIGUREBMC
CREATE
DBPLAN
DESCRIBE
DETAIL
DROP
EXPORT
FLASHCACHE
FLASHCACHECONTENT
FOR REPLACEMENT
FORCE
GRIDDISK
IGNORE REDUNDANCY
IMPORT
INACTIVE
IORMPLAN
KEY
LED
LIST
LUN
MAIL
MEMORY
METRICDEFINITION
METRICCURRENT
METRICHISTORY
MS
NULL
OFF
ON
PHYSICALDISK
PRIVILEGE
REALM
RESTART
RS
RULE
SHUTDOWN
SNMP
STARTUP
THRESHOLD
USER
VALIDATE

If these keywords are used as values in commands, then they must be enclosed in quotation marks.

8.1.4 CellCLI Command-Line Editing

The CellCLI utility supports command-line history and editing, similar to BSD editline and GNU readline functionality. Most of the command editing features of CellCLI are similar to modern shells, such as bash and tcsh.

8.1.5 CellCLI Input and Output Options

Oracle Exadata Storage Server Software command-line utilities read commands from standard input and write output to standard output. You can use the host operating system options for redirecting input and output to compose and process command scripts. For example, you can perform the following redirection:

$ cellcli < command-script-in  > results-out

In this example, the output from CellCLI commands in the command-script-in file are written to the results-out file.

8.1.6 Comments in CellCLI Scripts

You can add single-line comments to CellCLI scripts using several formats. You can begin the comment line with REMARK,REM or -- (two hyphens).

For example, the following are valid syntax for comments:

REMARK This is a comment
REM This is a comment
-- This is a comment

8.1.7 Line Continuation in CellCLI Commands

To continue a long command on to the next line, insert a hyphen (-) at the end of the line. Then, press Enter, and continue typing the command.

For example:

CellCLI> LIST CELLDISK WHERE name LIKE 'CD_04.*' -
         ATTRIBUTES name, status, comment

8.2 About CellCLI Administration Commands

DBMCLI administrative commands do not act directly on objects.

The following administration commands are available with CellCLI:

Note:

The celladmin user should be used to run all services on the cell.The cellmonitor user is for monitoring purposes. The cellmonitor user can run the following commands:

  • DESCRIBE

  • EXIT

  • HELP

  • LIST

  • REMARK

  • SET

  • START

8.3 About CellCLI Object Commands

This section describes the CellCLI object commands, object types, and object attributes. The following CellCLI commands operate on Oracle Exadata Storage Server Software objects:

The preceding commands are described in detail later in this chapter.

8.4 About CellCLI Object Types

The following table lists the Oracle Exadata Storage Server Software object types that can be used with CellCLI object commands:

  • ACTIVEREQUEST — An active request provides a client-centric or application-centric view of client I/O requests that are currently being processed by a cell. The active request object can be used only with the LIST command.

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

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

  • CELL — Cell refers to the current or local cell. A cell is the server to which disks are attached and on which the CellCLI utility runs.

  • CELLDISK — Each cell disk is associated with a logical unit number (LUN). One physical disk is associated with each cell disk.

  • DATABASE — Database refers to an active database instance.

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

  • FLASHCACHE — The portion of flash storage allocated for use as a cache.

  • FLASHCACHECONTENT — List of all objects currently cached in the flash cache.

  • FLASHLOG — The portion of flash storage allocated for storing the Oracle Exadata Smart Flash Log.

  • GRIDDISK — A grid disk is a logical partition of a cell disk. It is exposed on the Oracle Exadata Storage Server network to the database hosts, where it becomes an Oracle ASM disk that can be used to create an Oracle ASM disk group.

  • IBPORT — The InfiniBand ports for Oracle Exadata Storage Server.

  • IORMPLAN — An I/O Resource Management interdatabase plan is a set of directives that determines allocation of I/O resources to database clients. There is one plan for the cell.

  • IORMPROFILE — I/O Resource Management interdatabase plans support profiles to ease management, and configuration of interdatabase plans for hundreds of databases. Profiles introduce a way to allocate I/O resources for a database.

  • KEY — A key is a unique hexadecimal string that identifies clients for security purposes.

  • LUN — Logical unit number (LUN) is the address for an individual physical disk device (a single-disk LUN). LUNs are automatically discovered when the cell is started. They are assigned to the corresponding cell disk when the cell disk is first created or when cell disks are discovered after the system is restarted. LUNs that are not yet assigned to a cell disk have a NULL value for the cellDisk attribute.

  • 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.

  • OFFLOADGROUP — An object that contains modifiable attributes of offload groups, and can be used to restart, start up, and shut down services.

  • PHYSICALDISK — A disk is called a physical disk on the cell. Physical disks can be listed, but they are not managed directly by CellCLI. Physical disks are automatically discovered and assigned to the corresponding cell disk when the cell disk is first created or when cell disks are discovered after the system is restarted.

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

  • QUARANTINE — A quarantine stops faulty SQL statements from performing a Smart Scan. This reduces software crashes, and improves storage availability.

  • ROLE — A named group of related privileges.

  • SOFTWAREHISTORY — A list of final states for past software updates.

  • SOFTWAREUPDATE — An object that contains the software location and time parameters for scheduling software updates

  • 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 — A person allowed access to the storage servers.

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

8.5 About Leading Zeros in Object Names

For commands that have the following format:

<verb> <object_type> <object_name>

the object name can be a number or string. For example, in the following command

list physicaldisk 0929M00Q8H

"list" is the verb, "physicaldisk" is the object type, and "0929M00Q8H" is the object name.

When the command parser analyzes commands, it can parse the object name as a string or as a number. For object names that begin with leading zeros, you need to surround the object name with either single or double quotes to force the parser to treat the object name as a string. Otherwise, the parser will treat the object name as a number and strip the leading zeros from the object name.

For example, the following command produced an error because the object name began with a 0 but was not quoted:

CellCLI> list physicaldisk 0929M00Q8H detail
CELL-04524: Physicaldisk object cannot be obtained for physical disk: 929M00Q8H

The parser removed the leading zero from 0929M00Q8H, and the command treated the object name as 929M00Q8H. This led to the error.

To avoid this transformation, surround the object name with either single or double quotes:

CellCLI> list physicaldisk "0929M00Q8H" detail

8.6 About CellCLI Object Attributes

Each CellCLI object has a set of attributes that are assigned when the object is created or altered.

Attribute filters and lists are used to specify which attributes and objects are displayed in the output of the LIST command.

All attributes can be displayed, but only some can be modified directly by the user. To display a list of attributes and determine which ones can be modified, use the DESCRIBE command.

Related Topics

8.6.1 Restrictions on Values of Common Attributes

The following restrictions apply to the values of attributes common to multiple CellCLI objects.

  • The value of the name attribute must be less than 256 characters and composed only of the following ASCII characters (alphanumeric and underscore only):

    • Lowercase alphabetic characters (a to z)

    • Uppercase alphabetic characters (A to Z)

    • Numbers (0 to 9)

    • Underscore (_)

  • The value of the comment attribute must be less than 256 characters.

See the syntax of each CellCLI command for any additional restrictions on attribute values.

8.6.2 Attribute Lists in LIST Command

You can specify which attributes to display for the LIST command with the following optional clause:

ATTRIBUTES { ALL | attribute1 [, attribute2] ... }

ALL displays all possible object attributes for the LIST object combination.

Example 8-1 Listing METRICHISTORY for Specific Attributes

This example shows the LIST METRICHISTORY command with the name and metrictype attributes specified, and the output.

LIST METRICHISTORY ATTRIBUTES name, metrictype
         CL_CPUT           Instantaneous
         CL_FANS           Instantaneous
         CL_RUNQ           Instantaneous
         CL_TEMP           Instantaneous
         N_NIC_RCV_SEC     Rate
         N_NIC_TRANS_SEC   Rate
...

8.6.3 Attribute Filters in LIST Commands

You can specify which objects to display with the LIST command using the following optional clause:

WHERE attribute-filter1 [AND attribute-filter2] ...

Each attribute-filterN has the following syntax:

attribute [ NOT | !] operator comparison_value

In the preceding syntax, the following arguments are used:

  • operator: The supported operators are listed in the following table. These operators can be combined with NOT or !.

    Table 8-1 Supported Operators in Attribute Filters

    Operator Description

    =

    Tests for equality between string, status, or numeric attributes. For example:

    status NOT = normal
    

    >

    Tests for values greater than the numeric attributes. For example:

    size > 139920M
    

    <

    Tests for values less than the numeric attributes. For example:

    freeSpace !< 100M
    

    LIKE

    Tests for a regular expression match with a string attribute using case-sensitive matching. For example:

    LIKE 'GD_IO_RQ.*'
    
  • comparison_value: When used with the supported operators, comparison_value is one of the following value types:

    • Numeric

    • Literal: Value such as active or normal

    • Datetime: Time value supported only for ALERTHISTORY

    • String: Value delimited by single quotation marks ('') or double quotation marks (" ")

    • NULL: Unassigned strings or empty lists

8.7 CellCLI Command Reference

CellCLI has both administrative and object commands.

The following commands are available with the CellCLI utility:

8.8 ALTER

Purpose

The ALTER command performs an action on or changes attributes of a single cell object or multiple Oracle Exadata Storage Server Software objects. The ALTER command can be used to change an attribute or to take an action upon the object.

Syntax

ALTER { object_type object_name [, object_name]... operation
      | attribute_name = attribute_value 
        [, attribute_name = attribute_value]...
     }

Usage Notes

The following arguments can be used with the command:

  • object_type can be the following:

    • ALERTHISTORY

    • CELL

    • CELLDISK

    • FLASHCACHE

    • GRIDDISK

    • IBPORT

    • IORMPLAN

    • LUN

    • PHYSICALDISK

    • QUARANTINE

    • SOFTWAREUPDATE

    • THRESHOLD

    • USER

  • object_name is the name or identifier of an alert history, cell, cell disk, grid disk, interdatabase plan, LUN, or threshold.

  • operation is a valid action for the specified object_type.

When multiple objects are the target of an ALTER command, there is the possibility of partial success. If an error occurs, then the command is interrupted, and the remaining objects are not changed.

8.8.1 ALTER ALERTHISTORY

Purpose

The ALTER ALERTHISTORY command changes the attributes of all or specified alert histories.

Syntax

ALTER ALERTHISTORY { ALL | alertid1  [,alertid2 ...]}
       examinedBy=user_name

Usage Notes

The following arguments can be used with the command:

  • alertidn: The identifier of the alerts to be changed.

  • user_name: The name of the user who acknowledged the alert.

Example 8-2 Altering ALERTHISTORY Attributes

This example shows the ALTER command used with the ALERTHISTORY object to update the examinedBy attribute. The examinedBy attribute is the only ALERTHISTORY attribute that can be modified.

CellCLI> ALTER ALERTHISTORY 1671443714 -
                            examinedBy="jdoe"

CellCLI> ALTER ALERTHISTORY ALL examinedBy="jdoe"

8.8.2 ALTER CELL

Purpose

The ALTER CELL command changes the attributes of the cell.

Syntax

ALTER CELL  {
  | SHUTDOWN SERVICES { RS | MS | CELLSRV | ALL } [IGNORE REDUNDANCY]
  | RESTART SERVICES  { RS | MS | CELLSRV | ALL } [IGNORE REDUNDANCY]
  | RESTART BMC
  | STARTUP SERVICES  { RS | MS | CELLSRV | ALL }
  | LED {ON | OFF}
  | VALIDATE { ASR | MAIL | SNMP | CONFIGURATION }
  | VALIDATE SYSLOGCONF selector.node
  | CONFIGUREBMC
  | BBU { DROP FOR REPLACEMENT | REENABLE }
  | attribute_name = attribute_value 
        [, attribute_name = attribute_value]...
  }

Usage Notes

The following table lists the arguments and options for the ALTER CELL command:

Argument Options Description

SHUTDOWN SERVICES

RS (Restart Server)

MS (Management Server)

CELLSRV [IGNORE REDUNDANCY] (Cell Server)

ALL [IGNORE REDUNDANCY]

All services are shut down, or the specified service is shutdown.

When the SHUTDOWN SERVICES ALL or SHUTDOWN SERVICES CELLSRV option is specified, then the following occurs:

  • All grid disks are made inactive and stop accepting user I/O.

  • Oracle ASM takes disks offline.

Communication between the cell, the database instance, and Oracle ASM instances is disrupted.

RESTART SERVICES

RS

MS

CELLSRV [IGNORE REDUNDANCY]

ALL [IGNORE REDUNDANCY]

Restart Server must be running before restarting individual services. If Restart Server is not running, then the only possible commands are STARTUP SERVICES {RS | ALL} or RESTART SERVICES {RS | ALL}.

RESTART BMC

none

Restarts the Baseboard Management Controller (BMC).

STARTUP SERVICES

RS

MS

CELLSRV

ALL

All services are started or the specified service in the command is started.

RS must be running before you can start other individual services. If RS is not running, then the only possible commands are STARTUP SERVICES {RS | ALL} or RESTART SERVICES {RS | ALL}.

LED

ON

OFF

LED ON and LED OFF operations turn on and off the chassis LED.

You can manually set the LED to light to indicate that a cell requires maintenance. The LED is also set to light automatically if a component fails.

VALIDATE

ASR

MAIL

SNMP

CONFIGURATION

The VALIDATE ASR operation sends a test from the storage server host to the Auto Service Request Manager.

The VALIDATE MAIL operation sends a test message using the e-mail attributes configured for the cell.

The VALIDATE SNMP operation sends a test message using the SNMP attributes configured for the cell. The VALIDATE SNMP TYPE=ASR operation validates ASR on Oracle Exadata Storage Server.

The VALIDATE CONFIGURATION operation validates the configuration. When the validation is complete and correct, the system responds with Cell cell_name successfully altered. If there is a problem, then the system responds with an error message.

VALIDATE SYSLOGCONF

facility.priority

The VALIDATE SYSLOGCONF facility.priority sends a test message for the specified facility and priority.

CONFIGUREBMC

none

Configures the BMC for hardware alerts to the local cell so that Management Server can pick up the alerts.

BBU

DROP FOR REPLACEMENT

ENABLE

BBU DROP FOR REPLACEMENT drops the hard disk controller battery-backed unit (BBU).

BBU REENABLE re-enables the BBU.

attributes

 

The attributes that can be changed using the ALTER CELL command are shown as modifiable in Example 8-75.

The following are additional usage notes for the ALTER CELL command:

  • You might need to restart, shut down, or start up a cell for the following reasons:

    • Software upgrades

    • Service outages that include any condition under which a cell is not responding to service requests

  • Before shutting down services, the system checks the status of the grid disks, as follows, depending on the command:

    • When an ALTER CELL SHUTDOWN SERVICES CELLSRV command is issued, the system checks the grid disks to determine if it is safe to shut down the CELLSRV service. If the asmDeactivationOutcome attribute returns yes for all grid disks, then the system inactivates the grid disks on the cell, and Oracle ASM takes the disks offline. After the offline process completes, CELLSRV is shut down. If any gird disk cannot be shut down, then the error message CELL-01548 appears, and CELLSRV continues to run.

    • The ALTER CELL SHUTDOWN SERVICES ALL command performs the same checks as described in the preceding bullet for the ALTER CELL SHUTDOWN SERVICES CELLSRV command. If the grid disks return no, then an error message appears, and the current state of MS, RS, and CELLSRV are displayed.

    • The ALTER CELL RESTART SERVICES CELLSRV and ALTER CELL RESTART SERVICES ALL command run the same checks to ensure that all disks can be deactivated safely from Oracle ASM. If the asmDeactivationOutcome attribute returns yes for all grid disks, then the CELLSRV service is restarted immediately, followed by a restart of the MS and RS services, if applicable.

  • The IGNORE REDUNDANCY option for the ALTER CELL command is only valid for the following:

    • ALTER CELL SHUTDOWN SERVICES CELLSRV IGNORE REDUNDANCY

    • ALTER CELL SHUTDOWN SERVICES ALL IGNORE REDUNDANCY

    • ALTER CELL RESTART SERVICES CELLSRV IGNORE REDUNDANCY

    • ALTER CELL RESTART SERVICES ALL IGNORE REDUNDANCY

    Note:

    The IGNORE REDUNDANCY option bypasses the asmDeactivationOutcome attribute checks. Using the IGNORE REDUNDANCY option results in immediate execution of the command. As a result, some Oracle ASM disk groups may be dismounted.

  • To set up the cell to send notifications about alerts, you can configure the following cell attributes:

    • smtpServer

    • smtpPort

    • smtpUser

    • smtpPwd

    • smtpUseSSL

    • smtpFrom

    • smtpFromAddr

    • smtpToAddr

    • snmpSubscriber

    • snmpUser

    • snmpEngineID

    • notificationMethod

    • notificationPolicy

    • emailSubscriber

    The smtpToAddr attribute can be used to set a list of comma-delimited e-mail addresses that are the recipients of the alert notification. The list must be enclosed in quotation marks.

    The snmpSubscriber attribute can be set to a list of SNMP targets to which the SNMP alert notification is sent. These targets are specified as follows:

    snmpSubscriber=(
      (host=host[,port=port][,community=community][,type=user_type][,fromIP="ip"][,asrmPort="ASRManager_port"])
    [,(host=host[,port=port][,community=community][,type=user_type][,fromIP="ip"][,asrmPort="ASRManager_port"])] ...)
    

    Note:

    • The ALTER CELL ... smnpSubscriber command replaces the existing value set for smnpSubscriber. To add to the list of SNMP targets ensure that you include the existing values in the command. The following message is displayed after running the command:

      snmpSubscriber <old_value> has been replaced with <new_value>
      

      For example:

      snmpSubscriber ((host=hosta)) has been replaced with ((host=hostb))
      
    • The snmpSubscriber attribute is used to configure Auto Service Request (ASR).

    • When specifying the snmpSubscriber attribute, the community name cannot contain spaces or the following characters: = ' " \ / < >

    • The SNMP alerts conform to MIBs (management information base) which are included with each installation of Oracle Exadata Storage Server Software. The MIB files on Oracle Exadata Storage Server are available at /opt/oracle/cell/cellsrv/deploy/config/.

      Type ASR and v3ASR alerts conform to SUN-HW-TRAP-MIB, which is available in the SUB-HW-TRAP-MIB.mib file.

      The other alert types conform to the cell_alert MIB, which is available in the cell_alert.mib file.

      The SNMP alerts and MIB conform to SNMP version 1 (SNMPv1). However, the Auto Service Request alerts conform to SNMP version 2c (SNMPv2c).

    The default value for port is 162. The default value for community is public.

    The snmpSubscriber types are ASR, v3, and v3ASR. For types v3 and v3ASR, a snmpUser must be defined, and the user name is provided instead of community.

    For the v3ASR type, the user must be defined with authProtocol = SHA, and privProtocol = AES. These are the only protocols supported by ASR Manager. Setting the snmpSubscriber as type v3ASR also sets the ILOM properties and rules for traps sent by ILOM.

    If type is not specified, the default is version 1, cell_alert traps. There is no string to specify this type. To use this type, just omit the type field.

    The fromIP field enables you to specify an IP address from which the trap is sent. If this field is not specified, it defaults to the IP address associated with eth0. Use this field if the default IP address is not registered with ASR Manager. ASR Manager only processes SNMP traps that are sent from IP addresses that it recognizes.

    The fromIP field is allowed only for SNMP subscribers whose type is either ASR or v3ASR.

    For example:

    CellCLI> alter cell snmpSubscriber=((host=asrhost,port=162,community=public,fromIP="1.1.1.1",type=ASR))
    

    The following example returns an error because the type is not ASR or v3ASR.

    CellCLI> alter cell snmpSubscriber=((host=localhost,port=162,community=public,fromIP="1.1.1.1"))
    CELL-00068: The fromIP field is only supported for ASR SNMP subscribers.
    

    The asrmPort field enables you to specify the port number on an ASR Manager machine that MS uses to communicate with ASR Manager. This port must be the same as the HTTP port of ASR Manager’s HTTP Receiver. You can check this by running asr show_http_receiver on the ASR Manager machine.

    The asrmPort field is allowed only for SNMP subscribers whose type is either ASR or v3ASR. The default value for this port is 16161.

    The snmpUser attribute defines the user who receives SNMP alerts. The syntax for the attribute is as follows:

    ((name=user1, authProtocol=auth_type, authPassword=*,                   \
    privProtocol=priv_type, privPassword=*) ,                               \
    (name=user2, authProtocol=auth_type, authPassword=*,                    \
    privProtocol=priv_type, privPassword=*, ), ...) 
    
    • name is the user name.

    • authProtocol is the authentication protocol. Options are MD5 or SHA.

    • privProtocol is encryption protocol. Options are none, AES, or DES. The default is none when the privProtocol attribute is not specified.

    • The authProtocol must be specified for the snmpUser attribute.

    • Only * is allowed for the password values in the command.

    • The system prompts for the authentication password. The authentication password must have 8 to 12 alphanumeric characters.

    • The system prompts for an encryption password if the encryption protocol is specified. The password is exactly 8 alphanumeric characters, and they are case sensitive.

    • Passwords are not stored or displayed. Secure hash keys are computed and used for trap authentication and encryption.

    • This command can only be run in interactive mode.

    The notificationMethod attribute value can be mail, snmp, none, or a combination of mail and snmp, such as notificationMethod='mail,snmp'. The default value is mail.

    The smtpUseSSL attribute enables Secure Socket Layer (SSL) encryption on the e-mail notifications when the attribute is set to true.

    The notificationPolicy attribute value can be none or a combination of critical, warning, or clear, such as notificationPolicy='warning,clear.'

    • The critical value refers to hardware-generated alerts or alerts generated by Automatic Diagnostic Repository (ADR) or BMC. The critical value also refers to a metric alert when the value exceeds the critical threshold specified in the metric definition.

    • The warning value refers to a metric alert when the value exceeds the warning threshold specified in the metric definition.

    • The clear value refers to a metric alert when the value is below the threshold boundary after having previously exceeded a warning or critical threshold.

    • The maintenance value refers to all hardware-related errors. The hardware errors are reported as "Maintenance" in e-mail message subject lines.

  • The ALTER CELL snmpSubscriber...type=asr command sets the Auto Service Request destination for Oracle Exadata Storage Server, and its ILOM. Removing all snmpSubscriber entries with type=asr from the SNMP subscriber list disables the trap mechanism for Oracle Exadata Storage Server and its ILOM.

  • For each subscriber, the host must be specified as either a domain name or an IP address. Enclose the host name or IP address in quotation marks if it contains non-alphanumeric characters. Port and community values are optional. The default port value is 162. The default community value is public. The type value is optional. The default value for type is NULL. The types ASR, V3, and v3ASR are the only supported non-NULL value.

  • After startup of the Management Server (MS), the snmpSubscriber list entries with type=asr are added to the ILOM for the cell. This ensures that when an ILOM is replaced, the entries are set for the new ILOM. If the entries are removed from the ILOM, then they must be manually added to the ILOM using the ALTER CELL ... snmpUser= command.

  • The snmpSubscriber with type=asr or type=v3ASR should only be configured to point to ASR Manager.

  • To validate that e-mail messages are successfully sent for cell alerts or events, use the ALTER command with the VALIDATE MAIL option. The validation process sends a test e-mail message to the configured recipient. If that test e-mail message is not received, then an e-mail configuration setting is not valid.

  • The emailFormat attribute can be html or text. By default, e-mail notifications are sent in HTML format. Change the value to text to receive plain text e-mail notifications.

  • The ALTER CELL snmpEngineID command is used by the SNMP managers to subscribe to alerts from the storage cells. The snmpEngineID parameter can be up to 20 characters. It should be unique for each target within a data center. The default is the cell name. This default is used if the snmpEngineID attribute is not set before the SNMP users are defined.

    The engine identifier should not be changed after SNMP users are defined. Any change to an engine identifier causes the user keys to be re-computed, and user passwords must be re-entered.

  • The ALTER CELL emailSubscriber command sets a list of comma-delimited e-mail addresses that are the recipients of alert notifications for specific alert types. The following is an example of the syntax:

    ALTER CELL emailSubscriber = ((email="email_address1",                \ 
               alertType="alert_type")                               \
              [, (email="email_address2",alertType="alert_type"), ...])
    

    The e-mail address must be a valid e-mail address. The email parameter is mandatory. The alertType parameter specifies the type of alert, and is optional. The alert types are HARDWARE, SOFTWARE, METRIC or ADR. If the alert type is not specified, then the subscription is for all alert types.

    An empty input string removes the current set of subscribers.

    The notification policy must be set before alert notifications can be received. The policy applies to all e-mail subscribers. The notification policy for these alerts are the same as for snmpSubscriber alerts.

  • If you change the cell name, then you must choose a unique cell name.

  • The bbuLearnCycleTime attribute is used to set the start time for the battery learn cycle. After the learn cycle has completed, the attribute reverts to its default quarterly cycle.

  • The bbuLearnSchedule attribute is used to set the next battery learn cycle. The following parameters are used with the bbuLearnSchedule attribute:

    • month: Values are 1 through 12. The month entered must be within the current month and the next three months. For example, if the bbuLearnSchedule attribute is set in February, then the months could be February, March, April or May.

    • week: Values are 1 through 5. The value 1 represents the first week of the month, 2 represents the second week, and so on. The week value must be specified when specifying month and day.

    • day: Values are 1 through 7. The value 1 represents Sunday, 2 represents Monday, and so on. The day value must be specified when specifying month and week.

    • date: Values are 1 through 31. The values represent the days of the month. The default date is 17.

    • hour: Values are 0 through 23. The value 0 represents 12:00 a.m., 1 represents 1:00 a.m., and so on.

    • minute: Values are 0 to 59. The values represent the minutes in an hour.

    • second: Values are 0 to 59. The values represent the seconds in a minute.

  • The ALTER CELL BBU DROP FOR REPLACEMENT command is run prior to replacement of a hard disk controller battery. The command changes the caching policy from writeback to writethrough, and turns on the locator LED. The new battery is enabled automatically.

  • The ALTER CELL BBU REENABLE command is run when a battery is removed and then the same battery is re-inserted. The command changes the caching policy from writethrough to writeback, and turns off the locator LED.

  • The ALTER CELL interconnectN="" command deletes information about interconnectN the system.

  • If the IP address to an InfiniBand interface is changed, then the command service openibd restart must be run as the root user before the service network restart command.

  • After changing an IP address, you must restart all services using the ALTER CELL RESTART SERVICES ALL command.

  • The syslogconf attribute extends syslog rules for a cell. The attribute can be used to designate that syslog messages be forwarded to a specified management server. On the management server, the forwarded messages are directed to a file, console, or management application, depending on the syslog configuration on the management server. The following shows the syntax for the attribute:

    syslogconf = ('selector @node' [, 'selector @node']... )
    

    In the preceding syntax, selector is the message type, and node is the specified server. Both variables follow syslog.conf standard syntax rules.

  • The facility option for the syslogconf attribute must be one of the following: auth, authpriv, cron, daemon, ftp, kern, lpr, mail, mark, news, security, syslog, user, uucp, local0, local1, local2, local3, local4, local5, local6, local7, none, and *.

  • The priority option for the syslogconf attribute must be one of the following: alert, crit, debug, emerg, err, error, info, notice, panic, warn, warning, none, and * (asterisk).

  • The ALTER CELL VALIDATE syslogconf selector command sends a test log message. The test message is directed as specified by rules in the /etc/syslog.conf file. If the syslogconf assignment extends the syslog rules, then a test message is forwarded to the specified management servers.

  • The flashCacheMode attribute is used to display and set the current value for flash cache. The values are writethrough (the default) or writeback. Note the following about the flashCacheMode attribute:

    • If the attribute is modified from writeback to writethrough and there is existing flash cache, then an error is displayed. The flash cache must be flushed and dropped before changing the attribute to writethrough.

    • If the attribute is to be modified from writethrough to writeback, then flash cache must be dropped before modifying the attribute.

    • Write back caching can be disabled on the grid disks that do not need caching, such as the grid disks in the RECO disk group. This allows other objects to use the cache space.

      See Also:

  • The ALTER CELL alertSummaryInterval command sets the frequency of the open alerts summary e-mail message. The open alerts e-mail message is an HTML document that provides a concise summary of all open issues on a cell even without access to the cell. Valid options are daily, weekly, biweekly and none.The default value is weekly.

  • The ALTER CELL alertSummaryStartTime command sets the delivery time for the open alerts summary e-mail message. The command accepts any valid time stamp.

  • The ALTER CELL eighthRack command enables or disables an eighth rack configuration on Oracle Exadata Database Machine X3-2 quarter racks or later. The options are true to enable the eighth rack configuration, and false to disable the eighth rack configuration. The ALTER CELL eighthRack=true command requires that there are no cell disks because enabling the eighth rack configures only half of the hard disks and flash capacity.

  • Flash cache compression is available in Oracle Exadata Storage Server Software releases 11.2.3.3.0 and later on Oracle Exadata Database Machine X4-2, and Oracle Exadata Database Machine X3-8 with Exadata Storage Server X4-2 (Sun Server X4-2L Servers).

  • The ALTER CELL flashCacheCompress command enables or disables flash cache compression. The options are true to enable flash cache compression, and false to disable flash cache compression. To enable flash cache compression on Oracle Exadata Database Machine X4-2, Oracle Exadata Database Machine X3-2, Oracle Exadata Database Machine X3-8 with Exadata Storage Server X3-2 (Sun Server X3-2L Servers), and Oracle Exadata Database Machine X3-8 with Exadata Storage Server X4-2 (Sun Server X4-2L Servers), use the following command:

    CellCLI> ALTER CELL flashCacheCompress=true 
    

    Note:

    Oracle Advanced Compression Option is required to enable flash cache compression.

    See Also:

    Oracle Exadata Database Machine Maintenance Guide for additional information about enabling flash cache compression

  • Flash cache compression must be disabled before a storage server is downgraded to an earlier release.

  • The ALTER CELL hardDiskScrubStartTime command sets the start time for proactive resilvering of latent bad sectors. Valid options are a date/time combination or now. The following table shows the approximate time needed to scrub one idle hard disk:

    Disk Type Hard Disk Capacity Approximate Time for Scrubbing

    High performance

    600 GB

    1 hour

    High performance

    1.2 TB

    2 hours

    High capacity

    2 TB

    4 hours, 40 minutes

    High capacity

    3 TB

    6 hours, 30 minutes

    High capacity

    4 TB

    8 hours

    High capacity

    8 TB

    13 hours

  • The ALTER CELL hardDiskScrubInterval command sets the interval for proactive resilvering of latent bad sectors. Valid options are daily, weekly, biweekly and none. Using the none option stops all disk scrubbing.

  • In the alert log, you may see messages such as "Begin scrubbing celldisk" and "Finished scrubbing celldisk". These informational messages are expected, and no action is necessary.

  • If the system is idle, disk scrubbing can drive the disk utilization to 100%. This is expected. Disk scrubbing will throttle itself using IORM based on disk activity. When requests come in, disk scrubbing activity will decrease. Customer workloads should not be affected by disk scrubbing.

  • The cell attribute values for the following attributes can be set to the default by using two sets of quotation mark characters as the value.

    • alertSummaryInterval

    • bbuLearnSchedule

    • hardDiskScrubInterval

    • notificationMethod

    • notificationPolicy

    • smtpPort

    • traceLevel

  • The ALTER CELL iotimeoutthreshold command changes the timeout threshold. If cell I/O takes longer than the defined threshold, then the I/O is cancelled, and Oracle ASM redirects the I/O to another mirror copy of the data. Any I/Os issued to the last valid mirror copy of the data are not cancelled, even if the timeout threshold is exceeded.

    The default value for iotimeoutthreshold is 1000s. The command takes a value, such as 5, and a unit. The valid unit is s, for seconds.

    Caution:

    Setting the timeout threshold too low can negatively impact system performance. Oracle recommends reviewing the Automatic Workload Repository (AWR) reports of peak I/O loads, and setting the threshold value to a value higher than the peak I/O latency with sufficient safety margin.

    To set up CA-certified security certificates on the cell for use with ExaCLI, use the following attributes:

    Note:

    The following attributes can be used only if you are running the ALTER CELL command from ExaCLI.

    • securityPubKey - Specifies the URL to the public key file.

    • securityPrivKey - Specifies the URL to the private key file.

    • securityPrivKeyPW - Specifies the password to use if the private key file is encrypted.

    For example:

    exacli> alter cell securityPubKey="http://www.acme.com/security/newkey.crt",  -
                       securityPrivKey="http://www.acme.com/security/newkey.key", -
                       securityPrivKeyPW=*
    
    password=****************
    

    After you upload the CA-certified security certificate, you must restart MS before the new security certificate is visible.

    cellcli> alter cell restart services ms
    

    See Also:

    "Using a CA-Certified Security Certificate" in Oracle Exadata Database Machine Maintenance Guide

  • You can turn off the diagnostic pack attachment to emails by running the following command:

    alter cell diagPackEmailAttach=FALSE
    

    See "CREATE DIAGPACK" for information about diagnostic packs.

  • The ramCacheMode attribute can be set to on, off, or auto. The default value is auto , which means the RAM Cache feature is not enabled. When you modify this attribute, you must restart CellSrv for the change to take effect.

Examples

Example 8-3 shows how to set the asrmPort field for an snmpSubscriber.

Example 8-4 shows how to enable and disable the auto diagpack upload feature.

Example 8-5 shows the ALTER command with the CELL object.

Example 8-6 shows how to set up e-mail notifications for the cell.

Example 8-7 shows how to set the InfiniBand interconnections.

Example 8-8 shows how to validate the e-mail setup on a cell.

Example 8-9 shows how to validate the Auto Service Request e-mail setup on a cell.

Example 8-10 shows how to change the format of e-mail messages.

Example 8-11 shows how to validate the SNMP setup on a cell.

Example 8-12 shows how to specify the type of e-mail alerts. In the example, one subscriber gets hardware and software alerts, and the other subscriber gets ADR alerts.

Example 8-13 shows how to modify the SNMP user.

Example 8-14 shows how to unsubscribe from e-mail alerts.

Example 8-15 shows how to validate the configuration on a cell.

Example 8-16 shows a sample error message when configuration on a cell is incorrect.

Example 8-17 shows how to start up and shut down cell services.

Example 8-18 shows how to set the LED on the cell.

Example 8-19 shows how to add a rule using the syslogconf attribute.

Example 8-20 shows how to add and validate a rule with test message.

Example 8-21 shows how to remove the syslog.conf rule.

Example 8-22 shows how to set the flash cache mode.

Example 8-23 shows how to set the frequency for the open alerts summary e-mail message to weekly.

Example 8-24 shows how to set the delivery time for the open alerts summary e-mail message.

Example 8-25 shows how to set the battery learn cycle. In the example, the command sets the battery learn cycle to occur January 17 3:00:59, and then the following learn cycles are April 17 3:00:59, July 17 3:00:59, and October 17 3:00:59. The default setting is "MONTH 1 DATE 17 HOUR 2 MINUTE 0."

Example 8-26 shows how to enable flash cache compression on a cell in Oracle Exadata Database Machine X4-2.

Example 8-27 shows how to set the disk scrubbing start time.

Example 8-28 shows how to modify the interval for proactive resilvering of latent bad sectors to weekly.

Example 8-29 shows how to reset the notificationPolicy attribute to its default value.

Example 8-30 shows to reset the traveLevel to the deafult value.

Example 8-31 shows how to modify the iotimeoutthreshold setting.

Example 8-3 Setting the asrmPort for an snmpSubscriber

CellCLI> ALTER CELL snmpSubscriber=((host=host1,port=162,community=public,type=asr,asrmPort=16161))

Example 8-4 Enabling/Disabling Auto Diagpack Upload

You can enable or disable this feature by setting the diagPackUploadEnabled attribute on the cell object.

Set the attribute to false to disable this feature, true to enable it. The default is true.

CellCLI> ALTER CELL diagPackUploadEnabled=FALSE

Example 8-5 Altering Cell Name, IP Block, and Cell Number Attributes

CellCLI> ALTER CELL name=cell02, cellNumber=2

Example 8-6 Configuring E-Mail Notifications for a Cell

CellCLI> ALTER CELL smtpServer='my_mail.example.com',            -
                    smtpFromAddr='john.doe@example.com',         -
                    smtpFrom='John Doe',                         -
                    smtpToAddr='jane.smith@example.com',         -
                    snmpSubscriber=((host=host1),(host=host2)),  -
                    notificationPolicy='clear',                  -
                    notificationMethod='mail,snmp'

Example 8-7 Setting InfiniBand Interconnections

CellCLI> ALTER CELL interconnect1='ib0', interconnect2='ib1'

Example 8-8 Validating E-mail on a Cell

CellCLI> ALTER CELL VALIDATE MAIL

Example 8-9 Validating Auto Service Request E-mail on a Cell

CellCLI> ALTER CELL VALIDATE SNMP type=asr

Example 8-10 Changing the Format of E-mail Messages

CellCLI> ALTER CELL emailFormat='text'
CellCLI> ALTER CELL emailFormat='html'

Example 8-11 Validating SNMP on a Cell

CellCLI> ALTER CELL VALIDATE SNMP

Example 8-12 Specifying the Type of E-mail Alert

ALTER CELL emailSubscriber=                                             \
           ((email="email1@example.com",alertType="HARDWARE,SOFTWARE"), \
           (email="email2@example.com",alertType="ADR"))

Example 8-13 Modifying the SNMP User

CellCLI> ALTER CELL snmpuser = ((name=ASR, authprotocol=md5, authpassword=*,   \
                    privprotocol=AES, privpassword=*))
snmpUser ASR authpassword: password
Confirm snmpUser ASR authpassword: password
snmpUser ASR privpassword: password
Confirm snmpUser ASR privpassword: password

Example 8-14 Unsubscribing from E-mail Alerts

ALTER CELL emailSubscriber=""

Example 8-15 Validating Configuration on a Cell

CellCLI> ALTER CELL VALIDATE CONFIGURATION

Cell CD_01_cell01 successfully altered

Example 8-16 Checking an Incorrect Configuration on a Cell

CellCLI> ALTER CELL VALIDATE CONFIGURATION

CELL-02827: Cell configuration check for hardware and firmware encountered the
following issues:

ILOM check has detected the following issue(s):
    Attribute Name : ILOMVersion
    Required       : 3.0.6.10.a r49240
    Found          : 3.0.6.10.a r49385

Example 8-17 Starting Up and Shutting Down Cell Services

CellCLI> ALTER CELL STARTUP SERVICES CELLSRV
CellCLI> ALTER CELL STARTUP SERVICES ALL

CellCLI> ALTER CELL SHUTDOWN SERVICES MS
CellCLI> ALTER CELL SHUTDOWN SERVICES CELLSRV
CellCLI> ALTER CELL SHUTDOWN SERVICES CELLSRV IGNORE REDUNDANCY
CellCLI> ALTER CELL SHUTDOWN SERVICES ALL 
CellCLI> ALTER CELL SHUTDOWN SERVICES ALL IGNORE REDUNDANCY

CellCLI> ALTER CELL RESTART SERVICES CELLSRV
CellCLI> ALTER CELL RESTART SERVICES ALL
CellCLI> ALTER CELL RESTART SERVICES ALL IGNORE REDUNDANCY

Example 8-18 Setting the Cell LED Off and On

CellCLI> ALTER CELL LED OFF
CellCLI> ALTER CELL LED ON

Example 8-19 Using the syslogconf Attribute

CellCLI> ALTER CELL syslogconf=('*.err;authpriv.none @loghost', -
         '*.emerg @loghost')

Example 8-20 Adding and Validating a Rule

CellCLI> ALTER CELL syslogconf=('kern.crit @loghost')
CellCLI> ALTER CELL VALIDATE syslogconf   'kern.crit'

Example 8-21 Removing All syslog.conf Rules

CellCLI> ALTER CELL syslogconf=''

Example 8-22 Setting the Mode for Flash Cache

CellCLI> ALTER CELL flashcachemode = writeback

Example 8-23 Setting the Frequency for the Open Alert s Summary E-mail Message

CellCLI> ALTER CELL alertSummaryInterval=weekly

Example 8-24 Setting the Time for Open Alerts Message Delivery

CellCLI> ALTER CELL alertSummaryStartTime="2013-04-23T12:57:00-06:00"

Example 8-25 Setting the Battery Learn Cycle

CellCLI> ALTER CELL bbuLearnSchedule = "MONTH 1 HOUR 3 SECOND 59"

Example 8-26 Enabling Flash C ache Compression

CellCLI> ALTER CELL flashCacheCompress=true

Example 8-27 Setting the Start Time for Proactive Resilvering of Latent Bad Sectors

CellCLI> ALTER CELL hardDiskScrubStartTime='2013-08-07T21:19:22-07:00'

Example 8-28 shows how to set the disk scrubbing interval.

Example 8-28 Setting the Proactive Resilvering of Latent Bad Sectors Interval to be Weekly

CellCLI> ALTER CELL hardDiskScrubInterval=weekly

Example 8-29 shows how to set the default value for the notificationPolicy attribute.

Example 8-29 Setting the Default Value for the notificationPolicy Attribute

CellCLI> alter cell notificationPolicy=""

See Also:

Example 8-30 shows how to set the traceLevel value to its default value:

Example 8-30 Setting the traceLevel Value to its Default Value

CellCLI> ALTER CELL traceLevel=""

Example 8-31 shows how to set the iotimeoutthreshold value.

Example 8-31 Setting the iotimeoutthreshold Value

To set the iotimeoutthreshold to 5 seconds:

CellCLI> ALTER CELL iotimeoutthreshold = '5s'

To reset the iotimeoutthreshold to the default value:

CellCLI> ALTER CELL iotimeoutthreshold = ""

8.8.3 ALTER CELLDISK

Purpose

The ALTER CELLDISK command changes the attributes of all cell disks or the specified cell disks.

Syntax

ALTER CELLDISK { ALL [FLASHDISK | HARDDISK] | cdisk_name [, cdisk_name]... }
   {{FLUSH | CANCEL FLUSH} [NOWAIT]} | 
   { attribute_name = attribute_value 
        [, attribute_name = attribute_value]...
   }

Usage Notes

The attributes that can be changed with the ALTER command are shown as modifiable in Example 8-76.

  • The FLASHDISK option limits the ALTER CELLDISK command to cell disks that are flash disks.

  • The HARDDISK option limits the ALTER CELLDISK command to cell disks that are hard disks.

  • The FLUSH option synchronizes dirty data from the flash cache to the grid disks. Dirty data is data that has not been synchronized with the grid disk. Synchronization of dirty data can be a lengthy process, depending on the number of bytes to be synchronized. Use the following command to check the progress:

    LIST CELLDISK ATTRIBUTES name, flushstatus, flusherror
    
  • The ALTER CELLDISK ... FLUSH command must be run before exporting a cell disk to ensure that the dirty data is flushed from flash cache to the grid disks.

  • The FLUSH option stops new data from being cached on the flash cache until CELLSRV restarts, or the flush operation is canceled.

  • The CANCEL FLUSH option terminates an earlier flush operation, and reinstates caching.

  • When the ALTER CELLDISK ... FLUSH command is run for a flash cell disk, it synchronizes dirty data from the flash cache located on the specified FDOM to cached grid disks. When the command is run for a hard cell disk, it synchronizes dirty data from the flash cache located on all FDOMs to the grid disks located on the specified cell disk.

Example 8-32 Altering Cell Disk Attributes

This example shows how to change cell disk attributes.

CellCLI> ALTER CELLDISK cdiska name = CD_01_cell01, -
               comment = 'cdiska is now CD_01_cell01'

CellCLI> ALTER CELLDISK ALL -
               comment = 'This cell disk is on cell cell01'

CellCLI> ALTER CELLDISK ALL HARDDISK FLUSH NOWAIT

CellCLI > ALTER CELLDISK c9datafile1 CANCEL FLUSH 

8.8.4 ALTER FLASHCACHE

Purpose

The ALTER FLASHCACHE command flushes data not synchronized with the grid disks (dirty data) from flash cache on the specified disks.

Syntax

ALTER FLASHCACHE { ALL | CELLDISK="cdisk1 [,cdisk2] ..."}
      {SIZE} {FLUSH | CANCEL FLUSH} [NOWAIT] }

Usage Notes

  • The ALL option affects all available flash cell disks.

  • The CELLDISK option allows specific cell disks to be flushed.

  • When the SIZE option is specified with the ALL option, the size is validated. If the size is valid, then all cell disks are dropped, and flash cache is created with the specified size.

  • When the SIZE option is specified with the CELLDISK option, the size is validated. If the size is valid, then the specified cell disks are dropped, and the flash cache is created on the specified cell disks with the specified size.

  • The FLUSH option synchronizes dirty data from the flash cache to the grid disks. Dirty data is data that has not been synchronized with the grid disk. Synchronization of dirty data can be a lengthy process, depending on the number of bytes to be synchronized. Use the following command to check the progress:

    LIST CELLDISK ATTRIBUTES name, flushstatus, flusherror
    
  • The FLUSH option stops new data from being cached on the flash cache until CELLSRV restarts, or the flush operation is canceled.

  • The ALTER FLASHCACHE CELLDISK= ... FLUSH command does not flush the dirty data when the data cannot be read from the flash cache or written to disk. To flush the dirty data from the flash disk to grid disks use the ALTER GRIDDISK ... FLUSH command.

  • The CANCEL FLUSH option terminates an earlier flush operation, and reinstates caching.

  • The NOWAIT option allows the ALTER command to complete while the flush operation is in progress.

  • By default, 5 percent of space on Extreme Flash Exadata X5-2 storage servers is used for write back flash cache. Use the DROP FLASHCACHE and CREATE FLASHCACHE commands to change the value.

Example 8-33 Flushing Dirty Blocks from Flash Cell Disks

This example shows how to flush dirty blocks from all flash cell disks.

CellCLI> ALTER FLASHCACHE ALL FLUSH
Flash cache on FD_00_scac01cel07 successfully altered
Flash cache on FD_01_scac01cel07 successfully altered
Flash cache on FD_02_scac01cel07 successfully altered
...
Flash cache on FD_14_scac01cel07 successfully altered
Flash cache on FD_15_scac01cel07 fsuccessfully altered

8.8.5 ALTER GRIDDISK

Purpose

The ALTER GRIDDISK command changes the attributes of all grid disks or specified grid disks.

Caution:

Before changing the name of a grid disk that belongs to an Oracle ASM disk group, ensure that the Oracle ASM disk group is offline.

Syntax

ALTER GRIDDISK { ALL  [FLASHDISK | HARDDISK] |gdisk_name1 [, gdisk_name2]... }
   { ACTIVE    |INACTIVE | {FLUSH [NOWAIT] | CANCEL FLUSH} |
    attribute_name = attribute_value 
        [, attribute_name = attribute_value]...
   [NOWAIT]
   

Usage Notes

The attributes that can be changed with the ALTER GRIDDISK command are shown as modifiable in Example 8-82.

  • The FLASHDISK option limits the ALTER GRIDDISK command to grid disks that are flash disks.

  • The HARDDISK option limits the ALTER GRIDDISK command to grid disks that are hard disks.

  • The ACTIVE option notifies Cell Server to accept I/O as normal for the specified grid disks. The grid disks are visible to the database clients.

  • The INACTIVE option makes the grid disks visible to the cell administrator, but not visible to the database clients. CELLSRV treats the grid disks as if they were offline. This mode allows management operations on the grid disks. You can do upgrading and testing on the grid disks before making the grid disks visible to database users. This functionality is similar to starting up a database in RESTRICTED mode.

    Note:

    When a grid disk that is currently in use by a database client is made INACTIVE, Oracle ASM takes the corresponding Oracle ASM disk offline when I/Os to the disk fail. To make the disk usable again, make the grid disk ACTIVE in the cell, and then bring the corresponding Oracle ASM disk back online in Oracle ASM.

  • The FLUSH option synchronizes dirty data from the flash cache to the grid disks. Dirty data is data that has not been synchronized with the grid disk. Synchronization of dirty data can be a lengthy process, depending on the number of bytes to be synchronized. Use the following command to check the progress:

    LIST GRIDDISK ATTRIBUTES name, flushstatus, flusherror
    
  • The FLUSH option stops new data from being cached on the specified grid disks until CELLSRV restarts, or the flush operation is canceled.

  • The FLUSH option is valid for write back disks, not write through disks.

  • The CANCEL FLUSH option terminates an earlier d flush operation, and reinstates caching.

  • The NOWAIT option allows the ALTER command to complete while a resize or flush operation continues.

  • The length of a grid disk name is limited to 30 characters.

  • The size attribute can be specified to expand or reduce space allocated to a grid disk. The corresponding Oracle ASM disk must be resized separately.

    The size attribute is specified as a number in bytes, unless the suffix M (megabytes) or G (gigabytes) is included with the number value. Grid disk space is allocated in 16 MB units, referred to as allocation units. The actual size allocated is the size of the largest multiple of allocation units less than or equal to the specified size. The minimum value is 16 MB. Values less than 16 MB are rounded up to 16 MB.

  • A grid disk should not be renamed when the grid disk is being accessed. If you try to rename a grid disk when it is being accessed, then the operation fails. You can make the grid disk inactive or dismount the Oracle ASM disk group to stop access to the grid disk before renaming it.

  • When an interleaved grid disk is resized, the contents of the grid disk are moved to achieve the interleaved space allocation across the cell disk. The resizing operation can take a few minutes. You can choose to have the data movement proceed as a background process by using the NOWAIT option. Use the LIST GRIDDISK command to check the status.

  • The cachingPolicy attribute is used to change the flash caching policy of a grid disk. Before changing the caching policy from default to none, ensure there is no cached data in flash cache for the grid disk by using the ALTER GRIDDISK ... FLUSH command.

    Flash cache is not used with data files placed in a disk group composed of grid disks with their cachingPolicy set to none.

    configures the RECO disk group to have its grid disk's cachingPolicy set to none; therefore flash cache is not used for any data files placed in RECO.

    Write back caching can be disabled on the grid disks that do not need caching, such as the grid disks in the RECO disk group. This allows other objects to use the cache space. Use the following commands to flush the cache, and then set the cachingPolicy attribute to none:

    ALTER GRIDDISK grid_disk_name FLUSH
    ALTER GRIDDISK grid_disk_name CACHINGPOLICY="none"
    

    To re-enable caching on the grid disk, do the following:

    ALTER GRIDDISK grid_disk_name CANCEL FLUSH 
    ALTER GRIDDISK grid_disk_name CACHINGPOLICY="default"
    

    grid_disk_name is the name of the grid disk.

Examples

Example 8-34 Altering Grid Disk Attributes

This example shows the ALTER command with the GRIDDISK object.

CellCLI> ALTER GRIDDISK data1_CD_01_cell01, data2_CD_01_cell01
         comment = "This grid disk is on cell01"

CellCLI> ALTER GRIDDISK ALL INACTIVE

Example 8-35 Using the NOWAIT Option

This example shows the NOWAIT option being used to have data movement done as a background process.

CellCLI> ALTER GRIDDISK gd0 SIZE=40M NOWAIT
GridDisk gd0 alter in progress

See Also:

8.8.6 ALTER IBPORT

Purpose

The ALTER IBPORT command performs an action on all InfiniBand ports, or specified InfiniBand ports.

Syntax

ALTER IBPORT {ALL | ibport_name [, ibport_name] ...} RESET COUNTERS

Usage Notes

The RESET COUNTERS option resets all counters on the InfiniBand port.

Example 8-36 Altering IBPORT Attributes

This example shows the ALTER command with the IBPORT object.

CellCLI> ALTER IBPORT ALL RESET COUNTERS

         InfiniBand Port HCA-1:1 successfully altered.
         InfiniBand Port HCA-1:2 successfully altered.
 
CellCLI> ALTER IBPORT "HCA-1:1" RESET COUNTERS

         InfiniBand Port HCA-1:1 successfully altered.

8.8.7 ALTER IORMPLAN

Purpose

The ALTER IORMPLAN command updates the interdatabase plan and category plans for the cell. The directives determine the allocation of I/O resources to database clients. The ALTER IORMPLAN command is used to control disk and flash I/Os by database.

Syntax

ALTER IORMPLAN [dbPlan=(directive1[, directive2]...),]
               [catPlan=( directive1[, directive2]...)]}
               [objective='iorm_objective']

Usage Notes

The attributes that can be changed with the ALTER command are shown as modifiable in Example 8-84.

  • You can activate the interdatabase plan with the by setting the dbplan attribute. To deactivate the interdatabase plane, clear the dbplan attribute.

  • The directiveN for a database plan (dbPlan) is of the following format:

    ( name=db_or_category_name, [share=number] [,level=number, allocation=number]
    [,limit=number] [, role={ primary | standby }] [, flashcache={on|off}]
    [, flashLog={on|off}] [, flashcachemin=number] [, flashcachelimit=number] 
    [, flashcachesize=number] [, type={ database | profile }] )
    
    • The flashcachemin, flashcachesize, and flashcachelimit directives are applicable to interdatabase plans only. The directives specify their values in bytes, unless the suffix M (megabytes), G (gigabytes), or T (terabytes) is specified, for example, 300M, 150G, or 1T. The flashcache directive cannot be set to OFF when specifying the flashcachemin, flashcachelimit, or flashcachesize directives.

    • A database plan can be defined using one of the following configurations:

      • Use the share attribute to specify the relative number of shares for a database. The share attribute allows IORM to manage up to 1024 databases.

      • Use the allocation attribute to specify percentages for I/O distribution for each database. The allocation attribute allows IORM to manage up to 32 databases.

    • The name value cannot start with an underscore (_).

    • At least one attribute for must be specified for each name value. For example, name and limit, name and share, or name and flashcache.

    • To enable disk I/O management, specify share, level and allocation, or limit.

    • The role attribute indicates that the directive is applied only when the databases are in that database role. If the role attribute is not specified, then the directive is applied regardless of the database role. The role attribute cannot be used on dbPlan other directives. The role attribute must be the last attribute specified in the directive.

    • The limit attribute specifies the disk I/O utilization limit for databases. It is a value greater than zero, and less than or equal to 100.

      Note:

      The MAX_UTILIZATION_LIMIT attribute specifies the disk I/O utilization limit for consumer groups. Refer to Oracle Database Administrator's Guide and Oracle Database PL/SQL Packages and Types Reference for additional information about this attribute.

    • The flashcache attribute is used to prevent a database from using the flash cache. This ensures that flash cache space is reserved for mission-critical databases.

      Note:

      If the flashcache attribute is not specifically set to off for a database, then that database uses flash cache by default.

    • The flashLog attribute is used to prevent a database from using the flash log.

      Note:

      If the flashLog attribute is not specifically set to off for a database, then that database uses flash log by default.

    • Up to 1024 directives are allowed for each dbPlan. These directives include the mandatory other category directive.

      Note:

      Only 32 directives are allowed when using the level and allocation attributes.

    • The level value is 1 to 8.

    • For each level and each role, the total allocation value cannot exceed 100.

    • The other value is a distinguished database and category name. It refers to all clients that are not specifically named in other directives. At least one directive with name=other is required for dbPlan when using the allocation attribute or the CellCLI utility returns an error.

    • The default value is a distinguished database name. It refers to databases with identical share-based plans to avoid adding directives for each database. Any database that does have an explicit directive, uses the attribute values that are specified for the default directive.

    • If the dbPlan directive is not set, then the default is that each database has an equal percentage or share of the resources.

    • The default directive provides default values for all databases not explicitly named in a dbPlan.

    • The other directive can only be used with level and allocation, or limit attributes.

    • The share value is 1 to 32, with 1 being the lowest share, and 32 being the highest share.

    • The flashcachesize attribute specifies the guaranteed hard limit space in the flash cache for a database. This space in the flash cache is reserved but since this is a hard limit the database cannot exceed its quota even when the flash cache is not full.

      The sum of flashcachemin and flashcachesize across all the directives should be less than the size of flash cache.

    • The flashcachemin attribute value specifies the minimum guaranteed space in flash cache for a database.

    • The flashcachelimit attribute value specifies the maximum space in flash cache that a database can use. The flashcachelimit attribute is a soft limit that specifies the maximum space in the flash cache that a database can use. If the flash cache is not full, the database can exceed its allocated quota.

    • The flashcachemin, flashcachelimit, and flashcachesize attributes cannot be specified for category plans.

    • The type attribute must be set to either database or profile. If type in not specified, then the directive defaults to the database directive.

  • The directiveN for a category plan (catPlan) is of the following format:

    ( name=db_or_category_name, [,level=number, allocation=number]
    
    • The name value cannot start with an underscore (_).

    • At least one attribute for level, allocation or limit must be specified with the name value. For example, name and limit or name and level.

    • Up to 28 directives are allowed for each catPlan. These directives include the mandatory other category directive.

    • The level value is 1 to 8.

    • For each level and each role, the total allocation value cannot exceed 100.

    • The other value is a distinguished database and category name. It refers to all clients that are not specifically named in other directives. At least one directive with name=other is required for catPlan or the CellCLI utility returns an error.

    • If the catPlan directive is not set, then the default is that no category plan is used. The resources are divided among databases.

  • The objective option specifies the optimization mode for IORM. The objective option can be as follows:

    • low_latency: Use this setting for critical OLTP workloads that require extremely good disk latency. This setting provides the lowest possible latency by significantly limiting disk utilization.

    • balanced: Use this setting for critical OLTP and DSS workloads. This setting balances low disk latency and high throughput. This setting limits disk utilization of large I/Os to a lesser extent than low_latency to achieve a balance between good latency and good throughput.

    • high_throughput: Use this setting for critical DSS workloads that require high throughput.

    • auto: Use this setting to have IORM determine the optimization objective. IORM continuously and dynamically determines the optimization objective, based on the workloads observed, and resource plans enabled.

    • basic: Use this setting to disable I/O prioritization and limit the maximum small I/O latency.

  • To reset an interdatabase plan attribute to the default value, set the attribute to an empty string. Single quotation marks or double quotation marks can be used to set an empty string. The marks must match, for example "" is correct, but "' is incorrect.

  • Consider running ALTER IORMPLAN commands as scripts because of the length of the commands.

  • The following items should be checked before implementing a plan:

    • A catPlan must have at least one directive for other set.

    • A dbPlan must have at least one directive for other when using the allocation attribute.

    • A dbPlan does not use the other directive when using the share attribute.

    • Allocations are not greater than 100 for each level.

    • There are no more than 32 directives for dbPlans that use the allocation attribute.

    • There are no more than 1023 directives for dbPlans that use the share attribute.

    • There are no more than 28 directives for a catPlan.

    • The role directive is only used with dbPlans.

    • The role directive must be primary or standby.

    • The other directive cannot have role, flashcachemin, flashcachelimit, or flashcachesize attributes.

    • The flashcache, flashlog, flashcachemin, flashcachelimit and flashcachesize attributes are only for dbPlans.

    • The limit directive is only for dbPlans.

    • The total for the allocation directives are not greater than 100.

    • The value for a share directive is not greater than 32.

    • The sum of share directives is not greater than 32768.

    • The default directive does not include the level, allocation or role directives.

    • The type attribute can only be specified for interdatabase plans.

    • The type attribute must be database or profile.

    • Profile directives support the share, limit, flashcache, flashlog, flashcachemin, flashcachelimit, and flashcachesize attributes.

    • A profile name cannot be OTHER or DEFAULT. Those names are reserved words.

    • The flashcache attribute cannot be set to off when the flashcachemin, flashcachelimit, or flashcachesize attributes are set.

    • The flashcachelimit attributes cannot be set to 0.

Examples

Example 8-37 shows the ALTER command with the IORMPLAN object.

Example 8-38 and Example 8-39 show how to set dbPlan using the share directive. Both examples set the same resource allocations.

Example 8-39 uses the default directive to set the share allocation for databases sales01, sales02, and so on.

Example 8-40 shows how to set flash cache use with the IORMPLAN attributes.

Example 8-41 shows how to specify flash cache quotas using IORMPLAN attributes.

Example 8-42 shows how to reset the IORMPLAN attributes.

Example 8-43 shows how to reset the IORMPLAN attributes.

See Also:

Example 8-37 Altering IORMPLAN Attributes

CellCLI> ALTER IORMPLAN                                        -
        catPlan=(                                              -
                 (name=administrative, level=1, allocation=80),-
                 (name=interactive, level=2, allocation=90),   -
                 (name=batch, level=3, allocation=80),         -
                 (name=maintenance, level=4, allocation=50),   -
                 (name=other, level=4, allocation=50)          -
                ),                                             -
        dbPlan=((name=sales_prod, level=1, allocation=80),     -
                (name=finance_prod, level=1, allocation=20),   -
                (name=sales_dev, level=2, allocation=100),     -
                (name=sales_test, level=3, allocation=50),     -
                (name=other, level=3, allocation=50))

CellCLI> ALTER IORMPLAN                                                        -
         dbPlan=((name='sales1,sales2', level=1, allocation=30, role=primary), -
                 (name=sales1, level=1, allocation=20, role=standby),          -
                 (name=sales2, level=1, allocation=20, role=standby),          -
                 (name=other, level=3, allocation = 50))

ALTER IORMPLAN                                             -
dbPlan=((name=salesprod, share=4, role=primary),           -
        (name=salesprod, share=1, limit=50, role=standby)  -
        (name=finance, share=4)                            -
        (name=hr, share=2))

CellCLI> ALTER IORMPLAN                                         -
         catPlan=((name=interactive, level=1, allocation=90),   -
                  (name=batch, level=2, allocation=80),         -
                  (name=maintenance, level=3, allocation=50),   -
                  (name=other, level=3, allocation=50)          -

CellCLI> ALTER IORMPLAN objective='low_latency'

CellCLI> ALTER IORMPLAN objective='auto'

CellCLI> ALTER IORMPLAN                                        -
         dbplan=((name=db1, limit=50),                         -
                 (name=db2, limit=50),                         -
                 (name=other, level=1, allocation=25))

Example 8-38 Setting a Database Plan Using the share Directive

ALTER IORMPLAN                                                 -
dbplan=((name=sales01, share=4),                               -
        (name=sales02, share=4),                               -
        (name=sales03, share=4),                               -
        (name=fin01, share=4),                                 -
        (name=fin02, share=4),                                 -
        (name=fin03, share=4),                                 -
        (name=dev01, share=1, limit=50, flashLog=off),         -
        (name=dev02, share=1, limit=25, flashCache=off))

Example 8-39 Setting a Database Plan using the default Directive

ALTER IORMPLAN                                                 -
        (name=dev01, share=1, limit=50, flashLog=off),         -
        (name=dev02, share=1, limit=25, flashCache=off)        -
        (name=default, share=4))

Example 8-40 Setting Flash Cache Use with IORMPLAN Attributes

CellCLI> ALTER IORMPLAN                                        -
         dbPlan=((name=sales_prod, flashCache=on),             -
                 (name=sales_dev, flashCache=on),              -
                 (name=sales_test, flashCache=off),            -
                 (name=other, flashCache=off))

CellCLI> ALTER IORMPLAN                                                          -
         dbPlan=((name=oltp, level=1, allocation=80, flashCache=on),             -
                 (name=dss, level=1, allocation=20, limit=50, flashCache=off),   -
                 (name=other, level=2, allocation=100, flashCache=off))

Example 8-41 Specifying Flash Cache Quotas Using IORMPLAN Attributes

CellCLI> ALTER IORMPLAN                                                      -
         dbPlan=((name=prod, share=8, flashCacheMin=4096),                   -
                 (name=dev,  share=2, flashCacheMin=1G, flashCacheLimit=4G), -
                 (name=test, share=1, limit=40, flashCacheLimit=2048))

Example 8-42 Resetting IORMPLAN Attributes

CellCLI> ALTER IORMPLAN dbPlan="", catPlan=""
CellCLI> ALTER IORMPLAN dbPlan=""
CellCLI> ALTER IORMPLAN catPlan=""

Example 8-43 Resetting IORMPLAN Attributes

CellCLI> ALTER IORMPLAN dbPlan="", catPlan=""
CellCLI> ALTER IORMPLAN dbPlan=""
CellCLI> ALTER IORMPLAN catPlan=""

8.8.8 ALTER LUN

Purpose

The ALTER LUN command re-enables all LUNs or specified LUNs.

Syntax

ALTER LUN { ALL  | lun1 [ , lun2] ...  }
  REENABLE FORCE

Usage Notes

This command creates the cell disk and grid disk metadata on a replacement disk.

This command rebuilds redundancy for the system area of the system disks even when the system LUN is in a normal state.

Caution:

Data might be lost when using this command.

Example 8-44 Re-enabling a LUN

This example shows the ALTER command with the LUN object.

CellCLI> ALTER LUN 'x:7' REENABLE FORCE

CellCLI> ALTER LUN ALL REENABLE FORCE

8.8.9 ALTER OFFLOADGROUP

Purpose

The ALTER OFFLOADGROUP command enables you to alter modifiable attributes of offload groups, and also to restart, start up, and shut down services.

Syntax

ALTER OFFLOADGROUP { offloadgroup1 [,offloadgroup2, ...] }
{attribute_name = attribute_value [, attribute_name = attribute_value ...]]
| STARTUP | RESTART | SHUTDOWN }

Usage Notes

  • The offloadgroupN (where N is a number) parameters specify the names of the offload groups whose attributes you want to modify, or that you want to start, shut down, or restart.

  • The attribute_name and attribute_value parameters specify the name and value of the attribute you want to modify.

  • The STARTUP parameter specifies that the offload group(s) is to be started.

  • The RESTART parameter specifies that the offload group(s) is to be shut down, then started.

  • The SHUTDOWN parameter specifies that the offload group(s) is to be shut down.

Examples

Example 8-45 Updating the "Comment" Attribute

ALTER OFFLOADGROUP offloadgroup1 comment='System group'

Example 8-46 Starting up the Offload Group Named "offloadgroup1"

ALTER OFFLOADGROUP offloadgroup1 startup

Related Topics

8.8.10 ALTER PHYSICALDISK

Purpose

The ALTER PHYSICALDISK command prepares a disk for replacement.

Syntax

ALTER PHYSICALDISK { ALL [harddisk]  | disk_id1 [,disk_id2]  ...  }
 { DROP FOR REPLACEMENT [FORCE] | REENABLE }

Usage Notes

The DROP FOR REPLACEMENT option:

  • Is supported only for hot-pluggable disks

  • Checks if it is safe to proactively replace the specified disk. For example, if you attempt to drop the last good system disk, then replacing it would cause the system to crash.

  • Offlines the data grid disks on the physical disk if they exist

  • Flushes the flash cache store on the disk if it's part of flash cache

  • Flushes the disk controller cache if the disk is a hard disk

  • Prepares the device so that it can be removed online. For example, for flash devices this option powers off the associated PCIe slot.

  • If you use the FORCE option with DROP FOR REPLACEMENT, then this allows the command to proceed even if the software deems it unsafe.

The REENABLE option re-enables a normal physical disk that was dropped for replacement.

The SERVICELED option is now obsolete. If you use this option, you will get the error message CELL-04591.

Examples

Example 8-47 Dropping a Normal, Functioning Physical Disk

This example shows how to drop a physical disk.

CellCLI> ALTER PHYSICALDISK FLASH_5_1 DROP FOR REPLACEMENT

Example 8-48 Re-enabling a Physical Disk

This example shows how to re-enable a physical disk.

CellCLI> ALTER PHYSICALDISK 12:3 REENABLE

8.8.11 ALTER QUARANTINE

Purpose

The ALTER QUARANTINE command changes the attributes for a quarantine.

Syntax

ALTER QUARANTINE { ALL  | quarantine1 [,quarantine2]  ...  }
   attribute_name = attribute_value 
   [, attribute_name = attribute_value]...

Usage Notes

Only modifiable fields can be changed.

Examples

The following example shows the ALTER command with the QUARANTINE object.

Example 8-49 Altering a Quarantine

CELLCLI> ALTER QUARANTINE 12 comment='bugX'

8.8.12 ALTER SOFTWAREUPDATE

Software updates are scheduled by setting a modifiable SoftwareUpdate attributes.

Purpose

The ALTER SOFTWAREUPDATE command enables you to alter modifiable SoftwareUpdate attributes, to validate the pre-requirements for the software update, or to start the upgrade immediately.

You can also run the ALTER SOFTWAREUPDATE command using exacli.

Syntax

ALTER SOFTWAREUPDATE {VALIDATE PREREQ | UPGRADE [FORCE] | attribute = attribute value [,attribute = attribute value...]}

Options for the ALTER SOFTWAREUPDATE Command

Attribute Description
VALIDATE PREREQ

Run software update check pre-requirement steps now. This will download the software update pre-requirement code for the update specified by the store attribute. These checks are run automatically as part of update. Use this option only if you want to run prerequisite checks explicitly. Any error found will be displayed. A stateful alert will be raised if any error is found by the VALIDATE PREREQ command.

UPGRADE [FORCE]

Run the software update (including the pre-requirement steps) now, using the software location specified by the SoftwareUpdate store attribute. Use this command if you want to perform the update now rather than wait for the time specified by the SoftwareUpdate time attribute.

If FORCE is specified, then the upgrade continues despite any pre-requirement check errors.

attribute = attribute value

Modify the specified SoftwareUpdate attributes to the values provided.

Attributes for SOFTWAREUPDATE

Attribute Description
frequency

Cell updates can automatically be done periodically by setting the frequency attribute to the desired frequency. You can specify one of the following values: {daily | weekly | biweekly }. If a value is not specified for frequency, then the scheduled update is only done once.

name

The name of the patch to use in the update, which includes the software version string such as 18.1.1.0.0.171018.patch.zip. By default, the most recent cell update version in the store is retrieved and used for the software update. If there are multiple versions at the store site, then this attribute can be used to specify which version should be used.

Patches downloaded My Oracle Support use a different name format, for example p26875767_181100_Linux-x86-64.zip. If you are using Oracle Exadata System Software 18c (18.1.0) or 18c (18.1.1), then you must rename the downloaded patch file so it has a name like 18.1.1.0.0.171018.patch.zip.

store

A URL for the location of the software update file. MS finds and downloads the software update file using the protocol specified by the URL. You can use the following protocols for the store URL: HTTP, HTTPS, or FILE. The update software can be staged anywhere that is accessible from the cell’s management or InfiniBand network.

time

A future date and time at which the software update should be performed. The time can be specified as a local informal date and time, for example "1 AM, next Tuesday". If the date and time is valid then the output from setting this attribute shows the interpreted time in standard format with timezone offset, such as 2017-08-22T01:00:00-08:00.

If you set this attribute to the empty string "", it cancels the scheduled software update.

timeLimitInMinutes

A cell update may wait for other cells to complete in order to preserve disk group redundancy. By default, there is no limit on the amount of time which can be spent waiting to update. This attribute may be set to a positive, maximum integer which represents the number of minutes a cell will spend waiting to update. If a cell’s update does not start within the time specified by the limit, then the update is cancelled and an update alert is reported.

Usage Notes

  • The store attribute directs cells to a URL from which they can automatically download update software. Each cell downloads the software to its active partition, and then loads the software on its passive partition. The cells reboot to the new software version according to the desired schedule.

  • Software download and the prerequisite check will begin up to a week before the scheduled update time.

  • The update progress can be monitored by displaying the non-modifiable SoftwareUpdate status attribute.

  • Software updates do not occur if the upgrade software is already installed

  • You can use dcli or exacli to schedule and install updates using the ALTER SOFTWAREUPDATE command.

  • The Software Update feature supports using HTTPS transport for software downloads. When using HTTPS, TLS certificate checks are performed by default. If the remote server’s certificate cannot be validated then the following error is reported:

    CELL-00076: An error occurred during download of software update:
    source https://hostname:port is not available.
    CELL-00092: The store's TLS certificate cannot be authenticated with known CA certificates.
    

    This can happen if the remote server uses a self-signed certificate or if the remote server uses a certificate signed by a certificate authority (CA) that is not included in the cell’s CA store. You can use the following procedure to add a CA certificate to the cell’s CA store. This is a security setup step which requires shell access as root on the cell.

    1. Get a CA certificate that can verify the remote server. The certificate should be stored in PEM or DER file format.

    2. Copy the file to the cell at this directory: /etc/pki/ca-trust/source/anchors/

    3. Run following commands:

      update-ca-trust enable
      update-ca-trust extract
      

    Use man to get more information about the update-ca-trust command.

Examples

Example 8-50 Modifying the SoftwareUpdate time Attribute

Modify the scheduled time of the next software update to 1 a.m. on Thursday.

CellCLI> ALTER SOFTWAREUPDATE time = "1 AM Thursday"
Cell update is scheduled to begin at 2017-08-24T01:00:00-08:00

Example 8-51 Setting the SoftwareUpdate store Attribute

This example shows how to set the store attribute to a location that uses HTTPS protocol.

ALTER SOFTWAREUPDATE store="https://my-exa-store/cell"

Example 8-52 Starting a SoftwareUpdate Immediately

This example shows how to immediately start a software update using the attribute values already specified.

ALTER SOFTWAREUPDATE UPGRADE FORCE

8.8.13 ALTER THRESHOLD

Purpose

The ALTER THRESHOLD command updates the attribute values of all thresholds or the specified thresholds.

Syntax

ALTER THRESHOLD { ALL |threshold_name [, threshold_name ...] }
   attribute_name = attribute_value 
   [, attribute_name = attribute_value]...

Usage Notes

The attributes that can be changed with the ALTER command are shown as modifiable in Describing the THRESHOLD Object.

Examples

The following example shows how to alter threshold attributes.

Example 8-53 Altering Threshold Attributes

CellCLI> ALTER THRESHOLD ct_io_wt_rq.interactive warning=10, critical=20, -
                comparison='=', occurrences=2, observation=10

CellCLI> ALTER THRESHOLD ALL occurrences=3

Related Topics

8.8.14 ALTER USER

Purpose

The ALTER USER command changes the attributes of a user role.

Syntax

ALTER USER user1 attribute_name1 = attribute_value1      \
[, attribute_name2 = attribute_value2, ...]

Usage Notes

  • The user name cannot be root, celladmin or cellmonitor. Those are reserved.

  • The user name should be unique.

  • The system prompts for a password for the new user. The password must have 12 to 40 alphanumeric characters or special characters !@#$%^&*() with at least one digit, one lowercase letter, and one uppercase letter. Starting with Exadata Storage Server Software release 18.1.0.0.0, the password can be 8 to 40 characters in length and can also utilize the special characters - and _.

  • The new password cannot be the same as the current password for the user.

Example 8-54 Using the ALTER USER Command

This example shows how to change a user's password.

CellCLI> ALTER USER sjones password=TOPsecret2345

8.9 ASSIGN KEY

Purpose

The ASSIGN KEY command assigns or removes a security key to or from a client.

Syntax

ASSIGN KEY FOR [ASMCLUSTER] 'client1' = 'key-value1' [, 'client2' = 'key-value2'...]

ASSIGN KEY FOR [REMOTE | LOCAL] CELL 'client1' = 'key-value1' [, 'client2' = 'key-value2'...]

ASSIGN KEY FOR CELL 'key-value'

Usage Notes

  • clientN is the unique name (DB_UNIQUE_NAME) for a database client or the Oracle ASM cluster name, if the ASMCLUSTER keyword is specified.

    If you specify the ASMCLUSTER keyword, the Oracle ASM cluster name must not be longer than 14 characters, and only alphanumeric and the hyphen characters are allowed.

  • key-valueN is the hexadecimal string key that is assigned to the client as a security key. The key value is generated with the CREATE KEY command.

    • The key values assigned with the ASSIGN command must match the keys in the cellkey.ora files on the Oracle ASM and database host computers.

    • The key value can be the same for multiple clients.

    • An empty string for the key-valueN removes a previously assigned key.

  • For Oracle ASM-scoped security or database-scoped security, the clients must be entered in the availableTo attribute of the GRIDDISK object.

  • The optional keyword ASMCLUSTER indicates that the client is an Oracle ASM cluster.

    Note that if you specify a client name and key that already exist (that is, the same configuration for ASM-scoped security) and you use the ASMCLUSTER keyword, the client will be changed to be an ASM cluster client. In this case, the name and key will be removed from the ASM-scoped security list, and added as an ASM cluster client. Grid disks with this ASM client in their ACL can remain online for this operation.

  • The FOR LOCAL CELL clause assigns a cell key to the local (current) cell. If you specify FOR LOCAL CELL, there can be only one key; a list of values is not supported.

    The FOR REMOTE CELL clause specifies the cell keys that the current cell will accept.

    Cell keys enable cell-to-cell direct operations.

Examples

Example 8-55 Assigning and Removing Keys to and from Clients

This example shows the ASSIGN KEY command.

CellCLI> ASSIGN KEY FOR 'db0' ='b67d5587fe728118af47c57ab8da650a'

CellCLI> ASSIGN KEY FOR '+asm'='7c57ab8da650ab118587feaf467d5728'

CellCLI> ASSIGN KEY FOR  '+asm'='ed63f41779c262ddd34a00c0d83590b8',  -
                         'db1' ='118af47c57ab8da650ab67d5587fe728',  -
                         'db2' ='8a65313e8de6cd8bcbab7f4bdddb0498',  -
                         'db3' ='9140c767bd92d1b45783e7fe6520e6d'

CellCLI> ASSIGN KEY FOR 'db1'='', 'db2'='', 'db3'='', '+asm'=''

CellCLI> ASSIGN KEY FOR LOCAL CELL mykey='fa292e11b31b210c4b7a24c5f1bb4d32'

CellCLI> ASSIGN KEY FOR REMOTE CELL -
          'cellkey1'='b67d5587fe728118af47c57ab8da650a', -
          'cellkey2'='118af47c57ab8da650ab67d5587fe728'


CellCLI> ASSIGN KEY FOR CELL '4839deff903625aab394df7638e7b29a'

8.10 CALIBRATE

Purpose

The CALIBRATE command runs raw performance tests on cell disks, enabling you to verify the disk performance before the cell is put online.

Syntax

CALIBRATE [FLASHDISK | HARDDISK | LUN1 [, LUN2]] [FORCE]

Usage Notes

You must be logged on to the cell as the root user to run CALIBRATE.

The FORCE option enables you to run the tests when Cell Server is running. If you do not use the FORCE option, then Cell Server must be shut down. Running CALIBRATE at the same time as a Cell Server process impacts performance.

Use the FLASHDISK option to specify that only flash LUNs be calibrated.

Use the HARDDISK option to specify that only hard disk LUNs be calibrated.

Use the LUNn option to specify a list of LUNs by name be calibrated.

Examples

Example 8-56 Output from CALIBRATE Command with FORCE Option on Oracle Exadata Storage Server

This example shows the output when using CALIBRATE with FORCE option on Oracle Exadata Storage Server.

CellCLI> CALIBRATE FORCE
Calibration will take a few minutes...
Aggregate random read throughput across all hard disk luns: 1604 MBPS
Aggregate random read throughput across all flash disk luns: 4242.9 MBPS
Aggregate random read IOs per second (IOPS) across all hard disk luns: 4927
Aggregate random read IOs per second (IOPS) across all flash disk luns: 148695
Controller read throughput: 1608.05 MBPS
Calibrating hard disks (read only) ...
Lun 0_0  on drive [20:0      ] random read throughput: 153.41 MBPS, and 412 IOPS
Lun 0_1  on drive [20:1      ] random read throughput: 155.38 MBPS, and 407 IOPS
Lun 0_10 on drive [20:10     ] random read throughput: 155.32 MBPS, and 423 IOPS
Lun 0_11 on drive [20:11     ] random read throughput: 151.24 MBPS, and 427 IOPS
Lun 0_2  on drive [20:2      ] random read throughput: 152.70 MBPS, and 422 IOPS
Lun 0_3  on drive [20:3      ] random read throughput: 155.42 MBPS, and 423 IOPS
Lun 0_4  on drive [20:4      ] random read throughput: 153.14 MBPS, and 428 IOPS
Lun 0_5  on drive [20:5      ] random read throughput: 154.06 MBPS, and 424 IOPS
Lun 0_6  on drive [20:6      ] random read throughput: 150.82 MBPS, and 409 IOPS
Lun 0_7  on drive [20:7      ] random read throughput: 154.61 MBPS, and 426 IOPS
Lun 0_8  on drive [20:8      ] random read throughput: 154.46 MBPS, and 424 IOPS
Lun 0_9  on drive [20:9      ] random read throughput: 154.63 MBPS, and 426 IOPS
Calibrating flash disks (read only, note that writes will be significantly slower) ...
Lun 1_0  on drive [[10:0:0:0]] random read throughput: 269.11 MBPS, and 19635 IOPS
Lun 1_1  on drive [[10:0:1:0]] random read throughput: 268.86 MBPS, and 19648 IOPS
Lun 1_2  on drive [[10:0:2:0]] random read throughput: 268.68 MBPS, and 19645 IOPS
Lun 1_3  on drive [[10:0:3:0]] random read throughput: 268.92 MBPS, and 19640 IOPS
Lun 2_0  on drive [[12:0:0:0]] random read throughput: 269.78 MBPS, and 20436 IOPS
Lun 2_1  on drive [[12:0:1:0]] random read throughput: 269.69 MBPS, and 20394 IOPS
Lun 2_2  on drive [[12:0:2:0]] random read throughput: 269.04 MBPS, and 20439 IOPS
Lun 2_3  on drive [[12:0:3:0]] random read throughput: 269.51 MBPS, and 20420 IOPS
Lun 4_0  on drive [[9:0:0:0] ] random read throughput: 269.07 MBPS, and 19668 IOPS
Lun 4_1  on drive [[9:0:1:0] ] random read throughput: 269.24 MBPS, and 19697 IOPS
Lun 4_2  on drive [[9:0:2:0] ] random read throughput: 269.09 MBPS, and 19676 IOPS
Lun 4_3  on drive [[9:0:3:0] ] random read throughput: 269.03 MBPS, and 19681 IOPS
Lun 5_0  on drive [[11:0:0:0]] random read throughput: 268.06 MBPS, and 19714 IOPS
Lun 5_1  on drive [[11:0:1:0]] random read throughput: 268.24 MBPS, and 19696 IOPS
Lun 5_2  on drive [[11:0:2:0]] random read throughput: 268.33 MBPS, and 19717 IOPS
Lun 5_3  on drive [[11:0:3:0]] random read throughput: 268.14 MBPS, and 19693 IOPS
CALIBRATE results are within an acceptable range.
 
CALIBRATE stress test is now running...
Calibration has finished.

Example 8-57 Calibrating LUNs by Name

CALIBRATE '2_1', '2_3' FORCE

Related Topics

8.11 CREATE

Purpose

The CREATE command creates a new object and assigns initial attributes to the object.

Syntax

CREATE object_type [name] ... 
   [attribute_name = attribute_value [, attribute_name = attribute_value]...]

Usage Notes

  • object_type can be as follows:

    • CELL

    • CELLDISK

    • FLASHCACHE

    • FLASHLOG

    • GRIDDISK

    • KEY

    • QUARANTINE

    • ROLE

    • THRESHOLD

    • USER

  • name is the name of the new object.

  • attribute_name is the name of a modifiable attribute for the object_type.

  • attribute_value is the initial setting for the attribute.

  • When multiple objects are valid as the target of a CREATE command, there is the possibility of partial success. If an error occurs, then the command is interrupted, and the remaining objects are not created.

8.11.1 CREATE CELL

Purpose

The CREATE CELL command creates a cell object and assigns initial attributes to the object.

Syntax

CREATE CELL [name]
   interconnect1=intValue1 [, interconnect2=intValue2 ...]
   [, attributeName = attributeValue  ...]

Usage Notes

The attributes that can be set are shown as modifiable in Describing the CELL Object.

  • This command can be used to assign the ASR value to the snmpSubscriber attribute.

    When specifying the snmpSubscriber attribute, the community name cannot contain spaces or the following characters: = ' " \ / < >
  • The default cell name is set to the network host name of the cell with hyphens in the network name replaced with underscores. You can display the network name with the uname -n command. If you change the cell name, then you must choose a unique cell name.

  • One to four interconnects can be specified. The interconnect1 attribute must be specified if the interconnect2 attribute is specified. The interconnect1 and interconnect2 attributes must be specified if interconnect3 is specified, and so on.

  • Interconnects are InfiniBand (ibN).

  • By default, the CREATE CELL command creates Exadata Smart Flash Cache cell disks on all flash LUNs, and creates Exadata Smart Flash Cache on the cell disks. Users can specify FLASHCACHE=0 to bypass creation of flash cell disks and Exadata Smart Flash Cache on the cell disks. A non-zero value for Exadata Smart Flash Cache is taken as the total size for creating Exadata Smart Flash Cache. The size is divided evenly across the flash LUNs.

  • The CREATE CELL command creates Oracle Exadata Smart Flash Log on the cell disks. Users can specify FLASHLOG=0 to bypass creation of flash logs on the cell disks. A non-zero value for Oracle Exadata Smart Flash Log is taken as the total size for creating Oracle Exadata Smart Flash Log files. The size is divided evenly across the flash LUNs.

  • The CREATE CELL eighthRack command enables or disables an eighth rack configuration on Oracle Exadata Database Machine X3-2 quarter racks or later. The options are true to enable the eighth rack configuration, and false to disable the eighth rack configuration. The CREATE CELL eighthRack=true command requires that there are no cell disks because enabling the eighth rack configures only half of the hard disks and flash capacity.

  • The CREATE CELL flashCacheCompress command creates a cell with or without flash cache compression. Flash cache compression maximizes the amount of data in cache, and improves the cache hit rate. The options are true to create a cell with flash cache compression enabled, and false to create a cell without flash cache compression. The system must be restarted in order to change flash cache compression.

    Note:

    Flash cache compression is not available on Oracle Exadata Database Machine X2-2 or Oracle Exadata Database Machine X2-8 racks.

Examples

Example 8-58 Creating a Cell

This example shows how to create a cell. In the example, the interconnections are set to existing InfiniBand connections.

CellCLI> CREATE CELL cell22 interconnect1=bond0

CellCLI> CREATE CELL cell22          -
            interconnect1=bond0, -

Example 8-59 Creating an Eighth Rack Configuration

This example shows how to create an eighth rack configuration on a quarter rack.

CellCLI> CREATE CELL interconnect1=bondib0, eighthRack=true 

8.11.2 CREATE CELLDISK

Purpose

The CREATE CELLDISK command creates a cell disk object and assigns initial attributes to the object. You can use the ALL option to automatically create cell disks.

Syntax

CREATE CELLDISK  {  
   ALL [FLASHDISK | HARDDISK] 
  |cdisk1 attribute_name=value,[attribute_name=value]... [FORCE]
  |((name=cdisk2,attribute_name=value,[attribute_name=value]...)
  [,(name=cdisk3,attributename=value,[attributename=value]...)]...)
  }

Usage Notes

The attributes that can be specified during creation are the cell disk name (cdiskN), comment, lun, and physicalDisk.

  • Either lun or physicalDisk is required when adding a specifically-named cell disk.

    • When a physical disk is provided, a single-disk LUN is created, and that LUN is used to create the cell disk. The LUN is flagged as automatically-created.

    • When a LUN is provided, that device is used to create the cell disk.

  • CREATE CELLDISK ALL is a shortcut command to create all candidate cell disks for the cell. This operation occurs in two steps:

    • All physical disks that are not already configured as LUNs are configured as single-disk LUNs (SDLs). These LUNs are flagged as automatically-created LUNs.

    • All LUNs that are not configured as cell disks are used to create cell disks. These cell disks are initially named according to the template CD_lunname_cellname. This name can later be changed using the ALTER CELLDISK command.

      Note:

      LUNs with a second or third extended file system (ext2/ext3) are ignored during the CREATE CELLDISK ALL operation.

  • The FLASHDISK option limits the CREATE CELLDISK command to cell disks that are flash disks.

  • The HARDDISK option limits the CREATE CELLDISK command to cell disks that are hard disks.

  • The list form of CREATE CELLDISK enables you to add a series of cell disks in a single command.

  • The FORCE keyword overrides the following error conditions:

    • The physical disk provided is already part of an existing LUN.

    • The LUN provided is already associated with a cell disk.

    FORCE causes the LUN to be reused to create the new cell disk. Any preexisting configuration is lost. FORCE is not an option for CREATE CELLDISK ALL or for the list form of CREATE CELLDISK.

  • The INTERLEAVING option should be used when you want to use interleaved grid disks. Setting this parameter to normal_redundancy or high_redundancy changes the manner in which the cell disk sectors are allocated to grid disks.

    When using the normal_redundancy interleave option, the creation of a grid disk with an offset creates half of the grid disk at the start of the outermost tracks at the offset specified, and the other half of the grid disk at the same offset from the start of the innermost tracks.

    With high_redundancy interleave option, the grid disk is divided into three equal-size sections, with each section going into the outermost third tracks, next outer third tracks and the innermost third tracks.

Cell disks are created automatically using the CREATE CELLDISK ALL command. This command creates single-disk LUNs from all available physical disks, and then creates cell disks from all available LUNs.

When a cell disk is created, metadata describing the cell disk is written to the cell disk itself and to the cell configuration files. Approximately 48 MB of the cell disk is allocated for the cell disk metadata partition. On a subsequent restart, Cell Server attempts to rediscover the created cell disk by reading configuration data on the disk. Any hardware changes in the cell might cause a change in the LUN and device name for a cell disk. The rediscovery mechanism that runs during the cell restart process changes the cell disk configuration accordingly.

Example 8-60 Creating a Cell Disk

CellCLI> CREATE CELLDISK ALL

CellCLI> CREATE CELLDISK cdisk03 lun=03

CellCLI> CREATE CELLDISK cdisk04 physicalDisk='I2:1:2'

CellCLI> CREATE CELLDISK CD_03_cell04 lun=03

CellCLI> CREATE CELLDISK CD_05_cell09 physicalDisk='2I:1:2'

CellCLI> CREATE CELLDISK CD_06_cell10 INTERLEAVING='normal_redundancy'

CellCLI> CREATE CELLDISK CD_07_cell11 INTERLEAVING='high_redundancy'

8.11.3 CREATE DIAGPACK

Purpose

The CREATE DIAGPACK command creates a diagnostic package, which contains logs and traces that you can use to troubleshoot problems in your system. You can also send the package to Oracle Support, as needed.

Syntax

CREATE DIAGPACK packStartTime=time, [durationInHrs=duration]

or

CREATE DIAGPACK alertName=alertName

Usage Notes

When an alert occurs, a diagnostic package is created automatically. This package contains logs and traces related to the alert.

The CREATE DIAGPACK command enables you to generate diagnostic packages manually.

  • The packStartTime parameter specifies when to start collecting the logs and traces. The format of packStartTime is yyyy_MM_ddTHH_mm_ss, For example: 2015_07_07T09_00_00.

    You can also specify the keyword nowfor packStartTime. The packStartTime cannot be in the future and cannot be older than 7 days. The value of packStartTime is used as part of the name of the diagnostic package.

  • The durationInHrs parameter specifies the number of hours of logs and traces to include in the diagnostic package. Valid values are from 1 (default) to 6.

    Every diagnostic package includes logs 1 hour before and 1 hour after the packStartTime. For example, if you specify a time of 12_00_00, then logs will collected from 11_00_00 to 13_00_00, unless the end time is in the future.

  • The alertName parameter specifies the alert name for which to create the diagnostic package. You can run the LIST ALERTHISTORY command to view the alert names.

Name of Diagnostic Packages

The name of the diagnostic package is formed as: hostname_diag_packStartTime_unique package ID

For example: testcell1_diag_2015_07_07T09_00_00_3

For alerts, the name of the diagnostic package is formed as: hostname_timestamp of when the package was created_alert ID. For example: testcell1_2015_09_30T13_13_00_2_1

Location of Diagnostic Packages

The location of the diagnostic packages is $LOG_HOME.

Status of Diagnostic Packages

You can run the LIST DIAGPACK command to get a list of diagnostic packages in your system, and their status.

Privileges Needed to Create, List, and Download Diagnostic Packages

There are certain privileges that are needed for working with diagnostic packages. Use CellCLI to grant the following privileges to a role:

  • Privilege to create diagnostic packages:

    grant privilege CREATE ON DIAGPACK to ROLE role
    
  • Privilege to list diagnostic packages and check their status:

    grant privilege LIST ON DIAGPACK to ROLE role
    
  • Privilege to download diagnostic packages:

    grant privilege DOWNLOAD ON DIAGPACK to ROLE role
    

You can then grant the role to users. For example, if you named your role diagpack_role, the following command grants the role to fred.

CellCLI> GRANT ROLE diagpack_role TO USER fred

During deployment, Oracle Exadata Deployment Assistant (OEDA) creates an Exadata storage software user called CELLDIAG. You can use this user to connect to a cell remotely using ExaCLI or REST API. This user has privileges to create, list, and download diagnostic packages.

Downloading Diagnostic Packages

You can download diagnostic packages using any of the following methods. Note that you need the DOWNLOAD ON DIAGPACK privilege before you can download diagnostic packages.

  • Using the REST API

    • To download the diagnostic package by name, use the following URL, where hostname specifies the host name of the cell and diagpackname specifies the name of the diagnostic package:
      https://hostname/diagpack/download?name=diagpackname
      

      If the user is not already logged in, the URL will prompt for a user name and password.

      Diagnostic packages can also be accessed at https://hostname/diagpack . For example: https://cell1.example.com/diagpack.

      The page then prompts the user to log in:

      User: fred
      Password: ********
      

      Based on the user's privileges, various sections of this page could be hidden:

      • The form to create a new diagpack will not be shown if the user does not have the CREATE ON DIAGPACK privilege.

      • Similarly, the list of alerts and their diagnostic packages will not be shown if the user does not have the LIST ON DIAGPACK privilege.

    • To download the diagnostic package by alert name, use the following URL, where hostname specifies the host name of the cell and alertName specifies the alert name of the diagnostic package:

      https://hostname/diagpack/download?alert=alertName
      

      The alert name is the same alert name that is used in AlertHistory. It looks like 1, 2, 3 for stateless alerts, and 1_1, 2_1, 3_1, 3_2 for stateful alerts.

  • Using the download ExaCLI command

    ExaCLI enables you to run CellCLI commands on storage nodes remotely from compute nodes.

    To run the download command, run the following commands on a compute node:

    1. Start up ExaCLI and connect to the cell containing the diagnostic pack. For example, use a command similar to the following where hostname specifies the host name of the cell:

      exacli -l celladministrator -c hostname
      Password=********
      
    2. Run the download command using a command similar to the following where name specifies the name of the diagnostic package to download and destinationFolder specifies the directory where you want to save the downloaded diagnostic package:

      exacli> download diagpack name destinationFolder
      
  • Getting the diagnostic package from the alert emails

    The alert emails include diagnostic packages for all alerts except INFO, CLEAR, and WARNING. Diagnostic packages are generated for critical alerts only.

Re-triggering Package Creation from the Web Page

You can use the following URL to re-trigger package creation:

https://hostname/diagpack

If the diagnostic package for an alert does not exist on disk, then the web page shows a Create Package link instead of a Download link.

Click the Create Package link to add the alert to the list for creating a diagnostic package. Once the diagnostic package has been created, and the web page is refreshed, the page will display a Download link that you can use to download the newly created diagnostic package.

Turning Off the Diagnostic Pack Attachment in Emails

To turn off the diagnostic pack attachment in emails, run ALTER CELL diagPackEmailAttach=FALSE. The diagnostic packs are still generated and stored on the storage servers. To download the diagnostic packs, see "Downloading Diagnostic Packages".

Examples

Example 8-61 Using "now" for packStartTime

This example creates a diagnostic package using now as the start time and the default duration of 1 hour.

The output is 1 compressed file under $LOG_HOME.

CellCLI> CREATE DIAGPACK packStartTime="now"
    Processing: scab01cel11_diag_2015_07_08T17_53_58_1
    Use 'list diagPack' to check its status.

Example 8-62 Specifying a duration

This example creates 3 diagnostic packages under $LOG_HOME:

The first package has a start time of 2015_07_07T09_00_00.

The second package has a start time of 2015_07_07T10_00_00.

The third package has a start time of 2015_07_07T11_00_00.

CellCLI> CREATE DIAGPACK packStartTime="2015_07_07T09_00_00", durationInHrs=3
    Processing: scab01cel11_diag_2015_07_07T09_00_00_1
    scab01cel11_diag_2015_07_07T10_00_00_1 (In queue...)
    scab01cel11_diag_2015_07_07T11_00_00_1 (In queue...)
    Use 'list diagPack' to check its status.

8.11.4 CREATE FLASHCACHE

Purpose

The CREATE FLASHCACHE command creates Exadata Smart Flash Cache on a cell for I/O requests.

Syntax

CREATE FLASHCACHE {[ALL [size = fc_size] | CELLDISK = 'cdisk1 [,cdisk2],,,'    \
   [, size=fc_size]} [attribute_name = attribute_value 
   [, attribute_name = attribute_value] ...]

Usage Notes

Cell disks defined on Exadata Smart Flash Cache cannot be exported.

The ALL argument creates Exadata Smart Flash Cache on all flash cell disks. If the ALL argument is not specified, then the CELLDISK argument must be specified.

Using the CELLDISK argument, you can specify a list of flash cell disks to be used for flash cache. The names of the flash cell disks are comma-delimited. The FLASHDISK argument is not required.

The size argument specifies the total space used for flash cache. Similar to space in grid disks and flash logs, flash cache space is allocated in 16 MB units, referred to as allocation units. If the size attribute is specified when creating a flash cache, then the size allocated is the size of the largest multiple of allocation units less than or equal to the specified size. For example, if 300M is specified for the size attribute, then 288 MB (16x18) is allocated because 288 is the largest multiple of 16 that is less than or equal to 300.

A minimum of 1 allocation unit is always allocated, so the minimum size for a flash cache is 16 MB. Any size value less than 16 MB is rounded up to 16 MB.

Before specifying the size attribute, ensure that you have first determined the available free space on each target flash cell disk with the LIST FLASHCACHE command. For example, LIST FLASHCACHE ATTRIBUTES freespace. If the size attribute is not specified, then the maximum size is allocated.

If the size attribute is not specified, then all available space on each cell disk in the list is used for Exadata Smart Flash Cache.

By default, 5 percent of space on Extreme Flash Exadata X5-2 storage servers is used for flash cache. To change the amount of space, it is necessary to drop the flash cache, and create it using the CREATE FLASHCACHE SIZE = command.

Examples

Example 8-63 Creating Exadata Smart Flash Cache

This example shows how to create Exadata Smart Flash Cache on a cell.

CellCLI> CREATE FLASHCACHE ALL

CellCLI> CREATE FLASHCACHE ALL SIZE=250g

CellCLI> CREATE FLASHCACHE CELLDISK='fd_01,fd_02,fd_03,fd_04'

CellCLI> CREATE FLASHCACHE CELLDISK='fd_01_mycell,fd_02_mycell', size = 64G

Related Topics

8.11.5 CREATE FLASHLOG

Purpose

The CREATE FLASHLOG command creates the Oracle Exadata Smart Flash Log on a cell for redo log I/O requests.

Syntax

CREATE FLASHLOG {[ALL {[FLASHDISK] |[size=log_size]} | CELLDISK='cdisk1 \
   [,cdisk2]...'  [, size=log_size]}

Usage Notes

The CREATE FLASHLOG command accepts a list of comma-delimited flash cell disks. If a size is specified in the command, then that size is divided evenly across the cell disks, and will total the specified size. If a size is not specified, then a default size of 512 MB is used.

The size of Oracle Exadata Smart Flash Log space on each flash disk must be less than 4 GB. If all 16 flash disks are available, then the total size of Oracle Exadata Smart Flash Log must be less than 64 GB.

Similar to space in grid disks and flash cache, flash log space is allocated in 16 MB units, referred to as allocation units. If the size attribute is specified when creating a flash log, then the size allocated is the size of the largest multiple of allocation units less than or equal to the specified size. For example, if 300M is specified for the size attribute, then 288 MB (16x18) is allocated because 288 is the largest multiple of 16 that is less than or equal to 300.

A minimum of 1 allocation unit is always allocated, so the minimum size for a flash log is 16 MB. Any size value less than 16 MB is rounded up to 16 MB.

The ALL FLASHDISK argument creates Oracle Exadata Smart Flash Log on all flash cell disks. If the ALL argument is not specified, then the CELLDISK argument must be specified. The FLASHDISK argument is not required.

Note:

The CREATE FLASHCACHE command, by default, uses all available space on each flash disk. Therefore, use the CREATE FLASHLOG command before creating the flash cache to ensure both objects consume the correct amount of flash disk space.

To change the size of the flash log, use the DROP FLASHLOG command to drop the flash log, and then use the CREATE FLASHLOG command to create a flash log with the new size.

Examples

The following example shows how to create Oracle Exadata Smart Flash Log on a cell.

Example 8-64 cCreating Oracle Exadata Smart Flash Log

CellCLI> CREATE FLASHLOG ALL

CellCLI> CREATE FLASHLOG ALL SIZE=1g

CellCLI> CREATE FLASHLOG ALL FLASHDISK

CellCLI> CREATE FLASHLOG CELLDISK='fd1,fd2,fd3,fd4'

8.11.6 CREATE GRIDDISK

Purpose

The CREATE GRIDDISK command creates a grid disk object on a specified cell disk or creates one grid disk on each cell disk on the cell. The command also assigns initial attributes to the new grid disks.

Syntax

CREATE GRIDDISK  {  ALL [FLASHDISK | HARDDISK] PREFIX=gdisk_name_prefix 
   | gdisk CELLDISK = attribute_value  }
   [, attribute_name = attribute_value]...

Usage Notes

The attributes that can be specified are the grid disk name (gdisk), CELLDISK, size, and comment. The CELLDISK argument is required when a single grid disk is created.

  • If an individual name is entered with the command, then the grid disk is created on the cell disk specified by the CELLDISK argument. You must ensure that the grid disk name is unique across all cells. If the disk name is not unique, then it might not be possible to add the grid disk to an Oracle ASM disk group.

  • The length of a grid disk name is limited to 30 characters.

  • The FLASHDISK option limits the CREATE GRIDDISK command to cell disks that are flash disks.

  • The HARDDISK option limits the CREATE GRIDDISK command to cell disks that are hard disks.

  • If the ALL PREFIX option is entered with the command, then one grid disk is created on each cell disk on the cell. PREFIX is required when ALL is used.

    The PREFIX option specifies the prefix assigned to the names of the created grid disks. The generated grid disk names are composed of the grid disk prefix followed by an underscore (_) and then the cell disk name in the following form:

    gdisk_name_prefix_cdisk_name
    

    Choose a prefix for the grid disk name that matches the Oracle ASM disk group to which the grid disk belongs to help you identify which disks belong to a disk group. The generated grid disk (gdisk_name_prefix_cdisk_name) must follow the restrictions on the name value.

    For example, if the Oracle ASM disk group name is data01, then data01 is used as the prefix for the grid disk names. If CREATE GRIDDISK ALL PREFIX=data01 is run on a cell with cell disks CD_01_cell01, CD_02_cell01, and CD_03_cell01, then grid disks are named data01_CD_01_cell01, data01_CD_02_cell01, and data01_CD_03_cell01 are created on each cell disk respectively.

  • The CREATE GRIDDISK ALL command skips disks which do not have enough free space for a minimum grid disk. A message stating which disks did not have enough free space appears, and the command continues.

  • The size and offset attributes are optional attributes specified as a number in bytes, unless the suffix M (megabytes), G (gigabytes), or T (terabytes) is included with the number, such as size=300M, or size=150G.

    Grid disk space is allocated in 16 MB units, referred to as allocation units. If the size attribute is specified when creating a grid disk, then the size allocated is the size of the largest multiple of allocation units less than or equal to the specified size. For example, if 300M is specified for the size attribute, then 288 MB (16x18) is allocated because 288 is the largest multiple of 16 that is less than or equal to 300.

    A minimum of 1 allocation unit is always allocated, so the minimum size for a grid disk is 16 MB. Any size value less than 16 MB is rounded up to 16 MB.

    Before specifying the size attribute, ensure that you have first determined the available free space on each target cell disk with the LIST CELLDISK command. For example, LIST CELLDISK cdisk ATTRIBUTES freespace. If the size attribute is not specified, then the maximum size is allocated.

    Offset determines the position on the disk where the grid disk is allocated. The outermost tracks have lower offset values, and these tracks have greater speed and higher bandwidth. Offset can be explicitly specified to create grid disks that are relatively higher performing than other grid disks. If offset is not specified, then the best (warmest) available offset is chosen automatically in chronological order of grid disk creation. You should first create the grid disks that are expected to contain the most frequently accessed (hottest) data, and then create the grid disks that contain the relatively colder data.

  • The value of the availableTo attribute is set to the names of the clients that you want to set up for database-scoped security. These clients were assigned security keys that match keys in the configuration files on the hosts.

    The value entered for a client name is the unique name (DB_UNIQUE_NAME). The specified clients are those that are allowed to access the grid disk. If a value is entered for availableTo, then only the specified clients have access to the grid disk; otherwise, any client can have access.

  • There is no need to edit the value of idp.type or idp.boundary. Oracle Exadata Storage Server Software passes a hint to Oracle ASM about the type of interleaved grid disk, either normal redundancy or high redundancy. Oracle ASM sets the default value for idp.type to static and idp.boundary to the type of redundancy used in the underlying grid disks. The default value of the idp.type attribute is static for Oracle Exadata Storage Server disk groups created on interleaved grid disks.

  • The cachingPolicy attribute can be set to default or none. The default option allows the data to be cached in flash cache for the grid disk. The none option means that flash cache is not used for data for the grid disk.

    Flash cache is not used with data files placed in a disk group composed of grid disks with their cachingPolicy set to none.

    Oracle Exadata Deployment Assistant (OEDA) configures the RECO disk group to have the cachingPolicy of its grid disks set to none; therefore flash cache is not used for any data files placed in the RECO disk group.

  • The virtualSize attribute is used to create the SPARSE disk group. The maximum virtual size for a sparse grid disk is approximately 100 TB. Sparse grid disks are available for Oracle Exadata Database Machine X3-2 and later.

    Note:

    The database and grid infrastructure must be release 12.1.0.2.0 BP5 or later when using sparse grid disks.

Example 8-65 Creating a Grid Disk

This examples shows how to create grid disks.

CellCLI> CREATE GRIDDISK data1_CD_01_cell01 CELLDISK=CD_01_cell01, size=200G

CellCLI> CREATE GRIDDISK data2_CD_02_cell01 CELLDISK=CD_02_cell01, size=200G

CellCLI> CREATE GRIDDISK data3_CD_03_cell01 CELLDISK=CD_03_cell01

CellCLI> CREATE GRIDDISK ALL PREFIX=data01, -
         availableTo='+asm,db1,db2'

CellCLI> CREATE GRIDDISK hr7_CD_07_cell01 CELLDISK=CD_07_cell01, -
         availableTo='asm_hr,hrdb0'

CellCLI> CREATE GRIDDISK GD123 CELLDISK=RECO_CD123, size=100G, cachingPolicy=none

Example 8-66 Creating a SPARSE Disk Group

CellCLI> CREATE GRIDDISK spar01 celldisk=CD_01_cel01, size=10G, virtualsize=100G

8.11.7 CREATE KEY

Purpose

The CREATE KEY command creates and displays a random hexadecimal string to assign client keys. The use of CREATE KEY ensures that the security key is in the correct format. This command provides a way to generate a key in the correct format, and it can be run on any cell.

Syntax

CREATE KEY

Usage Notes

The security key must be entered in the cellkey.ora configuration file on the computer hosts that contain clients for which you want to authorize access to a cell.

The key is also assigned to clients that access grid disk storage.

The key must be copied manually to the hosts and cells.

Example 8-67 Creating a Key

This example shows the CREATE command with the KEY object.

CellCLI> CREATE KEY
         3452c64fec9a5800bbe48d4093269400

8.11.8 CREATE QUARANTINE

Purpose

The CREATE QUARANTINE command allows a quarantine to be created manually.

Syntax

CREATE QUARANTINE quarantineType=value quarantinePlan="SYSTEM", 
                  dbUniqueName=value[, attributename=value]... 

Usage Notes

Manual creation of quarantines should be done in coordination with Oracle Support Services. In general, manual quarantines are created to proactively isolate SQL statements that are known to cause problems.

  • quarantineType specifies the type of quarantine to be created, such as SQLID and SQL_PLAN.

  • quarantinePlan must be set to SYSTEM. Oracle Support Services may specify other values.

  • dbUniqueName specifies the name of the database that has the quarantine.

Example 8-68 Creating a Quarantine

This example shows the CREATE command with the QUARANTINE object.

CELLCLI> CREATE QUARANTINE  DBUG comment='For debugging quarantines"

CellCLI> CREATE QUARANTINE quarantineType="SQLID", quarantinePlan="SYSTEM", -
         dbUniqueName="DB1", sqlid="5xnjp4cutc1s7";

Related Topics

8.11.9 CREATE ROLE

Purpose

The CREATE ROLE command creates a role for a user accessing a cell.

Syntax

CREATE ROLE  role_name1 [, role_name2, ...]

Usage Notes

The role name should be unique.

Example 8-69 Creating a Role

This example shows how to create a role named gd_monitor.

CellCLI>CREATE ROLE gd_monitor

8.11.10 CREATE THRESHOLD

Purpose

The CREATE THRESHOLD command creates a threshold object that specifies the conditions for generation of a metric alert.

Syntax

CREATE THRESHOLD name attributename=value [, attributename=value]...

Usage Notes

The attributes that can be specified are comparison, critical, occurrences, observation, and warning.

  • The name argument is required. The name is comprised of a metric name and an object name with the format metricName.objectName, such as db_io_rq_sm_sec.db123 or ct_io_wt_rq.interactive. Use the LIST METRICCURRENT metric command to display the available object name for metric. The object name is optional.

  • When a object name is not specified, then the threshold is applied to all metric objects for the given metric.

  • The comparison attribute is required with a condition value. The value must be '<', '<=', '=', '>=', or '>'.

  • The occurrences attribute specifies the number of consecutive measurements over the threshold value that trigger a state change.

  • The observation attribute is the number of measurements over which measured values are averaged.

  • A state change to the value set in warning or critical causes a stateful alert to be generated.

  • The CL_TEMP, CL_FSUT, and GD_SP_PRCT_ALLOCATED metrics have built-in thresholds, and automatically send alerts. Create thresholds for other metrics to receive alerts for those metrics.

When specifying occurrences and observations, you need the specified number of consecutive occurrences of sample averages over the number of observations to cause an alert. For example, if the following five observations (observations=5) happen on a cell, then the average sample would be 10 because the number of consecutive occurrences (occurrences=2) had values of 5 and 15.

Observation 1: 0
Observation 2: 30
Observation 3: 0
Observation 4: 5
Observation 5: 15

Example 8-70 Creating a Threshold

This example shows how to create a threshold.

CellCLI> CREATE THRESHOLD db_io_rq_sm_sec.db123 comparison='>', critical=120

CellCLI> CREATE THRESHOLD ct_io_wt_sm.interactive warning=10, critical=20, -
         comparison='=', occurrences=2, observation=5

8.11.11 CREATE USER

Purpose

The CREATE USER command creates a user.

Syntax

CREATE USER name PASSWORD = *

Usage Notes

  • The user name should be unique.

  • celladmin, cellmonitor, and root are reserved user names that cannot be used with the CREATE USER command.

  • The system prompts for a password for the new user. The password must have 12 to 40 alphanumeric characters or special characters !@#$%^&*() with at least one digit, one lowercase letter, and one uppercase letter. Starting with Exadata Storage Server Software release 18.1.0.0.0, the password can be 8 to 40 characters in length and can also utilize the special characters - and _.

  • The new password cannot be the same as the current password for the user.

Example 8-71 Creating a User

This example shows how to create a user.

CellCLI> CREATE USER agarcia PASSWORD = *
password: 
Confirm password: password
User agarcia successfully created.

8.12 DESCRIBE

Purpose

The DESCRIBE command displays a list of attributes for the object type that is provided as an argument. The list of attributes indicates whether each attribute can be modified.

Syntax

DESCRIBE object_type

Usage Notes

  • The object_type is one of the supported object types described in About CellCLI Object Types.

  • The list of attributes can be used as arguments in the LIST command.

  • DESCRIBE does not display all of the attributes for the objects.

8.12.1 DESCRIBE ACTIVEREQUEST

Purpose

The DESCRIBE ACTIVEREQUEST command displays a list of attributes for the ACTIVEREQUEST object type.

Syntax

DESCRIBE ACTIVEREQUEST

Usage Notes

The following table lists the attributes for the DESCRIBE ACTIVEREQUEST command.

Table 8-2 DESCRIBE ACTIVEREQUEST Attributes

Attribute Description

asmDiskGroupNumber

Number of the Oracle ASM disk group.

asmFileIncarnation

Incarnation number of the Oracle ASM file.

asmFileNumber

Number of the Oracle ASM file.

consumerGroupID

Identifier of the consumer group.

consumerGroupName

Name of the consumer group.

dbID

Database unique name.

dbName

Database name.

dbRequestID

Identifier of the database request.

fileType

File type associated with the request.

id

Unique identifier of the active request.

instanceNumber

Instance number associated with the request.

ioBytes

Number of bytes of I/O against the grid disk in the current session.

ioBytesSoFar

Number of total bytes of I/O.

ioGridDisk

Grid disk used by a request.

ioOffset

Measure of the offset on the grid disk.

ioReason

Reason for I/O activity, such as a control-file read.

ioType

Type of active request, such as file initialization, read, write, predicate pushing, filtered backup read, or predicate push read.

name

Unique name of the active request.

objectNumber

Object number associated with the request.

parentID

Identifier of the parent request.

requestState

State of the active request, such as the following:

  • Accessing Disk

  • Computing Result

  • Network Receive

  • Network Send

  • Queued Extent

  • Queued for Disk

  • Queued for File Initialization

  • Queued for Filtered Backup Read

  • Queued for Network Send

  • Queued for Predicate Pushing

  • Queued for Read

  • Queued for Write

  • Queued in Resource Manager

sessionID

Identifier of the session.

sessionSerNumber

Serial number of the database session.

sqlID

Identifier of the SQL command associated with the request.

tableSpaceNumber

Tablespace number associated with the request.

Example 8-72 Describing the ACTIVEREQUEST Object

This example shows the DESCRIBE command with the ACTIVEREQUEST object.

CellCLI> DESCRIBE ACTIVEREQUEST

         name
         asmDiskGroupNumber
         asmFileIncarnation
         asmFileNumber
         consumerGroupID
         consumerGroupName
         dbID
         dbName
         dbRequestID
         fileType
         id
         instanceNumber
         ioBytes
         ioBytesSofar
         ioGridDisk
         ioOffset
         ioReason
         ioType
         objectNumber
         parentID
         requestState
         sessionID
         sessionSerNumber
         sqlID
         tableSpaceNumber

8.12.2 DESCRIBE ALERTDEFINITION

Purpose

The DESCRIBE ALERTDEFINITION command displays a list of attributes for the ALERTDEFINITION object type.

Syntax

DESCRIBE ALERTDEFINITION

Usage Notes

The following table lists the attributes for the DESCRIBE ALERTDEFINITION command.

Table 8-3 DESCRIBE ALERTDEFINITION Attributes

Attribute Description

alertShortName

Abbreviated name for the alert. If the alert is based on a metric, then the short name is the same as the corresponding metric name attribute.

alertSource

Source of the alert, such as BMC or ADR.

alertType

Type of the alert. Values are stateful or stateless.

  • Stateful alerts are automatically cleared on transition to normal.

  • Stateless alerts are never cleared. You can change the alert by setting the examinedBy attribute.

description

Description for the alert.

metricName

Metric name if the alert is based on a metric.

name

Identifier for the alert.

Examples

The following example shows the DESCRIBE command with the ALERTDEFINITION object.

Example 8-73 Describing the ALERTDEFINITION Object

CellCLI> DESCRIBE ALERTDEFINITION

         name
         alertShortName
         alertSource
         alertType
         description
         metricName

8.12.3 DESCRIBE ALERTHISTORY

Purpose

The DESCRIBE ALERTHISTORY command displays a list of attributes for the ALERTHISTORY object type.

Syntax

DESCRIBE ALERTHISTORY

Usage Notes

The following table lists the attributes for the DESCRIBE ALERTHISTORY command.

Table 8-4 DESCRIBE ALERTHISTORY Attributes

Attribute Description

alertAction

Recommended action to perform for this alert.

alertMessage

Brief explanation of the alert.

alertSequenceID

Unique sequence ID for the alert. When an alert changes its state, such as warning to critical or critical to clear, another occurrence of the alert is created with the same sequence number and a time stamp of the transition.

alertShortName

Abbreviated name for the alert. If the alert is based on a metric, then the short name is the same as the corresponding metric name attribute.

alertType

Type of the alert. Values are stateful or stateless.

  • Stateful alerts are automatically cleared on transition to normal.

  • Stateless alerts are never cleared. You can change the alert by setting the examinedBy attribute.

beginTime

Time stamp when an alert changes its state.

endTime

Time stamp for the end of the period when an alert changes its state.

examinedBy

Administrator who reviewed the alert.

failedMail

Intended e-mail recipient when a notification failed.

failedSNMP

Intended SNMP subscriber when a notification failed.

metricObjectName

Object, such as cell disk or grid disk, for which a metric threshold has caused an alert.

metricValue

Value of the metric that caused the alert.

name

Unique identifier for the alert.

notificationState

Number indicating progress in notifying subscribers to alert messages:

  • 0: never tried

  • 1: sent successfully

  • 2: retrying, up to 5 times

  • 3: 5 failed retries

  • 4: the diagnostic packaging and the outgoing alert email are still pending for this alert. It is used by MS to keep track of the alerts that have not been processed or are being processed. This enables MS, in the event of a restart, to continue processing alerts with state 4 and send the alert email.

sequenceBeginTime

Time stamp when an alert sequence ID is first created.

serviceRequestNumber

The service request number associated with the alert.

serviceRequestLink

The URL to the service request associated with the alert.

severity

Severity level. Values are clear, info, warning, or critical.

Examples

The following example shows the DESCRIBE command with the ALERTHISTORY object.

Example 8-74 Describing the ALERTHISTORY Object

CellCLI> DESCRIBE ALERTHISTORY

         name
         alertAction
         alertMessage
         alertSequenceID
         alertShortName
         alertType
         beginTime
         endTime
         examinedBy              modifiable
         failedMail
         failedSNMP
         metricObjectName
         metricValue
         notificationState
         sequenceBeginTime
         serviceRequestNumber
         serviceRequestLink
         severity

Related Topics

8.12.4 DESCRIBE CELL

Purpose

The DESCRIBE CELL command displays a list of attributes for the CELL object type.

Syntax

DESCRIBE CELL

Usage Notes

The following table lists the attributes for the DESCRIBE CELL command.

Table 8-5 DESCRIBE CELL Attributes

Attribute Description

accesLevelPerm

Specifies the access level at which the cell runs by default. It is either remoteLoginEnabled or remoteLoginDisabled.

accesLevelTemp

Duration of time in which the access level is temporarily changed from the setting of accessLevelPerm.

bbuStatus

Status of hard disk controller battery-backed unit (BBU).

bmcType

Name and version of the BMC.

cellsrvStatus

Status of Cell Server.

cellVersion

Release number of the cell software.

comment

User-supplied text string.

cpuCount

Number of CPUs on the cell.

dbPerfDataSuppress

Specifies which databases should not have their statistics reported in Automatic Workload Repository (AWR) reports.

diagHistoryDays

Number of days ADR files are retained. The default is 7 days.

diagPackEmailAttach

Whether a diagpack is included as an attachment in the alert email or not. The default is true.

diagPackUploadEnabled

Whether the auto diagpack upload feature is enabled or not. The default is true.

doNotServiceLEDStatus

 

eighthRack

Specifies whether Oracle Exadata Database Machine Eighth Rack configuration for storage cells is enabled or disabled.

emailFormat

File format for e-mail messages. The value can be html or text.

emailSubscriber

List of names that subscribe to the alert notifications

events

String for events++ that is passed to Cell Server for debugging and trace information purposes.

exacliEnabled

Specifies whether exacli is enabled or disabled.

fanCount

Count of working fans and total fans, displayed as working/total.

fanStatus

Status of the fan. The value can be normal, warning, or critical.

flashCacheCompress

Setting for flash cache compression. The value can be true or false.

flashCacheMode

Setting for flash cache. The value can be writethrough or writeback. The default is writethrough.

id

Global unique identifier (GUID) supplied by the hardware vendor.

interconnect1-8

Interconnect 1 to 8 for the cell. For example: bondeth0.

interconnectCount

Number of active InfiniBand network interconnects.

iorm_mode

I/O Resource Management objective for the cell.

iormBoost

Ratio of the cumulative number of positions in the I/O queue that were skipped because of IORM scheduling to the number of I/Os that where scheduled. This ratio is calculated by sampling the changes each minute in the two numbers.

IOTimeoutThreshold

Specifies the timeout threshold. If cell I/O takes longer than the defined threshold, then the I/O is cancelled, and Oracle ASM redirects the I/O to another mirror copy of the data.

ipaddress1–8

IP addresses 1–8 for the cell.

kernelVersion

Version of the host kernel software.

location

Physical location of the cell hardware supplied by the user.

locatorLEDStatus

Status of cell LOCATE LED. The value can be on or off.

makeModel

Make and model of the cell hardware supplied by the vendor.

memoryGB

The memory in gigabytes for the cell.

metricCollection

Indicator for whether Management Server performs metric collection. Values are TRUE or FALSE. If set to FALSE, then all collection and alert mining is stopped. The default setting is TRUE.

metricHistoryDays

Number of days metric history files are retained. The default is 7 days.

msStatus

Status of Management Server.

name

Unique name for the cell.

notificationMethod

Notification method for alerts. The value should be mail, snmp, none, or both mail and snmp.

notificationPolicy

Indicator for severity alerts to be sent to subscribers. The value for notificationPolicy should be none or any combination of critical, warning, and clear.

offloadEfficiency

Ratio of data accessed by the storage cell to the data that is processed by the database. Larger values mean more offloading to the cell. Also known as cell efficiency ratio.

The cell efficiency ratio starts at 1, and does not change until Cell Server (CELLSRV) is running and accessing disks. Then the ratio of the total MB accessed on the cell to the MB accessed on the host (for the cell) is computed every minute that CELLSRV is active by Management Server (MS). The ratio is averaged over the previous 24 hours, or less if MS has been running less than 24 hours. Hourly averages are stored so they are not lost during MS and CELLSRV outages.

powerCount

Count of power supplies, displayed as working/total.

powerStatus

Status of the power. The value can be normal, warning, or critical.

rackName

The name of the rack.

ramCacheMaxSize

 

ramCacheMode

 

ramCacheSize

 

releaseImageStatus

Indicator for knowing whether imaging is successful or not.

releaseTrackingBug

Patch number for the cell software, such as 11223344.

releaseVersion

Release number for the cell software, such as 11.2.2.3.0.

rescuePlan

A list of commands that you can run after a server rescue to restore settings, such as IORM plans, thresholds, and notifications, to the last known values.

rollbackVersion

 

rpmVersion

The RPM version of the cell.

rsStatus

Status of Restart Server.

securityCert

The certified identity of the cell. Either CA-certified identity or the default self-certified identity.

securityPrivKey

The URL to the private key file.

securityPrivKeyPW

The password to use if the private key file is encrypted.

securityPubKey

The URL to the public key file.

siteName

The site name for the cell.

smtpFrom

SMTP e-mail user name that appears in alert notifications.

smtpFromAddr

SMTP e-mail address from which alert notifications are sent.

smtpPort

SMTP e-mail server port used to send alert notifications.

smtpPwd

Password of the SMTP e-mail user that sends alert notifications.

smtpServer

SMTP e-mail server used to send alert notifications.

smtpToAddr

Address to which e-mail is sent. It can be a comma-delimited list in quotation marks to allow multiple subscribers to alerts.

smtpUser

SMTP e-mail user name that is displayed in alert notifications.

smtpUseSSL

Specification to use Secure Socket Layer (SSL) authentication.

snmpSubscriber

List of hosts that subscribe to the SNMP alert notifications.

snmpUser

Defines the user who receives SNMP alerts.

status

Status of the cell.

syslogConf

Designates syslog messages that should be forwarded to a specified management server. Uses the following syntax for the attribute, where selector is the message type, and node is the specified server:

syslogconf = (selector @node' [, 'selector @node']... )

Both selector and node follow syslog.conf standard syntax rules.

temperatureReading

Current temperature (Celsius) of the cell obtained from the BMC.

temperatureStatus

Status of the temperature. The value can be normal, warning, or critical.

traceLevel

Level for which trace messages are written. This can be a valid Java logging level (SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST) or a valid Oracle Diagnostic Logging (ODL) logging level (INCIDENT_ERROR:1, ERROR:1, WARNING:1, NOTIFICATION:1, NOTIFICATION:16, TRACE:1, TRACE:16, TRACE:32). The default is INFO.

upTime

Time (days, hours:minutes) since the system was restarted.

usbStatus

Status of the USB device.

Examples

The following example shows the DESCRIBE command with the CELL object.

Example 8-75 Describing the CELL Object

CellCLI> DESCRIBE CELL

        name                   modifiable
        accessLevelPerm        modifiable
        accessLevelTemp        modifiable
        bbuStatus
        cellsrvStatus
        cellVersion
        comment                modifiable
        cpuCount
        dbPerfDataSuppress     modifiable
        diagHistoryDays        modifiable
        diagPackEmailAttach    modifiable
        diagPackUploadEnabled  modifiable
        doNotServiceLEDStatus
        eighthRack             modifiable
        emailFormat            modifiable
        emailSubscriber        modifiable
        events                 modifiable
        exacliEnabled          modifiable
        fanCount
        fanStatus
        flashCacheCompress     modifiable
        flashCacheMode         modifiable
        id
        interconnect1          modifiable
        interconnect2          modifiable
        interconnect3          modifiable
        interconnect4          modifiable
        interconnect5          modifiable
        interconnect6          modifiable
        interconnect7          modifiable
        interconnect8          modifiable
        interconnectCount
        iormBoost
        IOTimeoutThreshold     modifiable
        ipaddress1
        ipaddress2
        ipaddress3
        ipaddress4
        ipaddress5
        ipaddress6
        ipaddress7
        ipaddress8
        kernelVersion
        location               modifiable
        locatorLEDStatus
        makeModel
        memoryGB
        metricCollection       modifiable
        metricHistoryDays      modifiable
        msStatus
        notificationMethod     modifiable
        notificationPolicy     modifiable
        offloadGroupEvents     modifiable
        powerCount
        powerStatus
        rackName               modifiable
        ramCacheMaxSize        modifiable
        ramCacheMode           modifiable
        ramCacheSize
        releaseImageStatus
        releaseTrackingBug
        releaseVersion
        rescuePlan             hidden
        rollbackVersion
        rpmVersion
        rsStatus
        securityCert           modifiable
        securityPrivKey        modifiable
        securityPrivKeyPW      modifiable
        securityPubKey         modifiable
        siteName               modifiable
        smtpFrom               modifiable
        smtpFromAddr           modifiable
        smtpPort               modifiable
        smtpPwd                modifiable
        smtpServer             modifiable
        smtpToAddr             modifiable
        smtpUser               modifiable
        smtpUseSSL             modifiable
        snmpSubscriber         modifiable
        snmpUser               modifiable
        status
        syslogConf             modifiable
        temperatureReading
        temperatureStatus
        traceLevel             modifiable
        upTime
        usbStatus

Related Topics

8.12.5 DESCRIBE CELLDISK

Purpose

The DESCRIBE CELLDISK command displays a list of attributes for the CELLDISK object type.

Syntax

DESCRIBE CELLDISK

Usage Notes

The attributes displayed by the DESCRIBE CELLDISK command can include:

  • comment: User comment for the cell disk.

  • creationTime: Time stamp when the cell disk was created.

  • deviceName: Operating system device name of the LUN used by the cell disk.

  • devicePartition: Operating system device name of the partition that is used by the cell disk.

  • diskType: The type of disk.

  • errorCount: Number of errors that occurred on the cell disk.

  • freeSpace: Amount of unused space available on the cell disk.

  • freeSpaceMap: Location and size of unused space on the cell disk.

  • id: Global unique identifier (GUID) that is generated when the cell disk is created.

  • interleaving: Set to normal_redundancy or high_redundancy to indicate that grid disks should be allocated using the interleaving policy.

  • lun: Identifier of the LUN on which the cell disk is located.

  • name: Unique name of the cell disk.

  • physicalDisk: Name of the physical disk on which the cell disk is located.

  • raidLevel: Value of the RAID level that is currently used on the LUN. For example, RAID 0.

  • size: Total size of the cell disk.

  • status: Current status of the cell disk, such as normal or importRequired.

Example 8-76 Describing the CELLDISK Object

This shows the DESCRIBE command with the CELLDISK object.

CellCLI> DESCRIBE CELLDISK

         name                    modifiable
         comment                 modifiable
         creationTime
         deviceName
         devicePartition
         diskType
         errorCount
         freeSpace
         freeSpaceMap
         id
         interleaving
         lun
         physicalDisk
         raidLevel
         size
         status

8.12.6 DESCRIBE DATABASE

Purpose

Displays the specified attributes for active databases.

Syntax

DESCRIBE DATABASE

Usage Notes

The attributes for the DESCRIBE DATABASE command include the following:

  • databaseID: The unique identifier for the database.

  • lastRequestTime: The time stamp of the last request from the database.

  • name: The database name.

  • profile: The IORM profile associated with the database.

Examples

The following example shows the DESCRIBE command with the DATABASE object.

Example 8-77 Describing the DATABASE Object

CellCLI> DESCRIBE DATABASE
         name
         databaseID
         lastRequestTime
         profile

8.12.7 DESCRIBE DISKMAP

Purpose

Displays the grid disk attributes for a physical disk.

Syntax

DESCRIBE DISKMAP

Usage Notes

The following table lists the attributes for the DESCRIBE DISKMAP command.

Table 8-6 DESCRIBE DISKMAP Attributes

Attributes Description

databaseID

The unique identifier for the database.

lastRequestTime

The time stamp of the last request from the database.

name

The database name.

Examples

The following example shows the DESCRIBE command with the DISKMAP object.

Example 8-78 Describing the DISKMAP Object

CellCLI> DESCRIBE DISKMAP

physicaldisk name
physicaldisk serial number
physicaldisk slotNumber
physicaldisk status
physicaldisk size
device partition
celldisk assiciated to each pd
all griddisk names present in ecah pd.
flashcache (if any)
flashlog (if any) 

8.12.8 DESCRIBE FLASHCACHE

Purpose

The DESCRIBE FLASHCACHE command displays a list of attributes for the FLASHCACHE object type.

Syntax

DESCRIBE FLASHCACHE

Usage Notes

The following table lists the attributes for the DESCRIBE FLASHCACHE command.

Table 8-7 DESCRIBE FLASHCACHE Attributes

Attribute Description

cellDisk

Cell disk names that contain Exadata Smart Flash Cache.

creationTime

Time stamp when the Exadata Smart Flash Cache was created.

degradedCelldisks

List of cell disks configured for cache but not currently available.

effectiveCacheSize

Usable cache size after deducting space on unavailable cell disks.

id

Global unique identifier (GUID) that is generated when the Exadata Smart Flash Cache is created.

name

Unique name of the Exadata Smart Flash Cache.

size

Total size of the Exadata Smart Flash Cache.

status

Current status of the Exadata Smart Flash Cache, such as normal, warning or critical.

Examples

The following example shows the DESCRIBE command with the FLASHCACHE object.

Example 8-79 Describing the FLASHCACHE Object

CellCLI> DESCRIBE FLASHCACHE

         name
         cellDisk
         creationTime
         degradedCelldisks
         effectiveCacheSize 
         id
         size
         status

8.12.9 DESCRIBE FLASHCACHECONTENT

Purpose

The DESCRIBE FLASHCACHECONTENT command displays a list of attributes for the FLASHCACHE object type.

Syntax

DESCRIBE FLASHCACHECONTENT

Usage Notes

The following table lists the attributes for DESCRIBE FLASHCACHECONTENT command.

Table 8-8 DESCRIBE FLASHCACHECONTENT Attributes

Attribute Description

cachedSize

Size, in bytes, cached for this object.

cachedKeepSize

Size, in bytes, cached in keep mode for this object.

dbID

Database unique name identifier.

dbUniqueName

Database unique name.

hitCount

Number of I/Os which read data from flash cache for this object.

hoursToExpiration

Time before this object is downgraded from keep section, if not accessed again.

missCount

Number of I/Os which read data from disk for this object.

objectNumber

Dictionary object number of the segment which contains the object in the database.

tableSpaceNumber

Tablespace number for the object number.

Examples

The following example shows the DESCRIBE command with the FLASHCACHECONTENT object.

Example 8-80 Describing the FLASHCACHECONTENT Object

CellCLI> DESCRIBE FLASHCACHECONTENT

         cachedKeepSize
         cachedSize
         dbID
         dbUniqueName
         hitcount
         hoursToExpiration
         missCount
         objectNumber
         tableSpaceNumber

8.12.10 DESCRIBE FLASHLOG

Purpose

The DESCRIBE FLASHLOG command displays a list of attributes for the FLASHLOG object type.

Syntax

DESCRIBE FLASHLOG

Usage Notes

The following table lists the attributes for DESCRIBE FLASHLOG command.

Table 8-9 DESCRIBE FLASHLOG Attributes

Attribute Description

cellDisk

Names of the cell disks that contain Oracle Exadata Smart Flash Log.

creationTime

Timestamp when Oracle Exadata Smart Flash Log was created.

degradedCelldisks

List of cell disks configured for Oracle Exadata Smart Flash Log, but not currently available.

effectiveSize

Size of available Oracle Exadata Smart Flash Log after deducting space on unavailable cell disks.

efficiency

Efficiency of Oracle Exadata Smart Flash Log expressed as a percentage.

id

Global unique identifier (GUID) generated when Oracle Exadata Smart Flash Log is created.

name

Unique name of Oracle Exadata Smart Flash Log.

size

Total size of Oracle Exadata Smart Flash Log.

status

Current status of Oracle Exadata Smart Flash Log, such as normal, warning or critical. Status normal indicates all flash disks are available. Status warning indicates some flash disks are not available. Status critical indicates all flash disks are unavailable.

Examples

The following example shows the DESCRIBE command with the FLASHLOG object.

Example 8-81 Describing the FLASHLOG Object

CellCLI> DESCRIBE FLASHLOG

         name
         id
         creationTime
         status
         size
         cellDisk
         degradedCelldisks
         effectiveSize
         efficiency

8.12.11 DESCRIBE GRIDDISK

Purpose

The DESCRIBE GRIDDISK command displays a list of attributes for the GRIDDISK object type.

Syntax

DESCRIBE GRIDDISK

Usage Notes

The attributes for the DESCRIBE GRIDDISK command include the following:

  • asmDeactivationOutcome: Indicator whether a grid disk can be deactivated without loss of data. A value of YES indicates the grid disk can be deactivated without data loss.

  • asmDiskgroupName: Name of the Oracle ASM disk group.

  • asmDiskName: Name of the Oracle ASM disk.

  • asmDiskSize: Size of the Oracle ASM disk.

    This attribute is available in Oracle Exadata Storage Server Software release 12.1.2.3.0 and later.

  • asmFailGroupName: Name of the Oracle ASM failure group.

  • asmModeStatus: Indicator shows the current Oracle ASM usage of a grid disk. Statuses are ONLINE, OFFLINE, DROPPED, UNUSED, SYNCING, or UNKNOWN.

  • availableTo: Names of the clients that can access this grid disk.

  • cachingPolicy: The flash caching policy for this grid disk. Values are default or none.

    • default means data for this grid disk uses the flash cache.

    • none means data for this grid disk do not use flash cache.

    The caching policy can be set when creating a grid disk, or using the ALTER GRIDDISK command.

  • cellDisk: Name of the cell disk that contains the grid disk.

  • comment: User-supplied text string.

  • creationTime: Time stamp when the grid disk was created.

  • diskType: The type of disk.

  • errorCount: Count of hardware errors detected by the cell disk containing this grid disk.

  • id: Global unique identifier (GUID) that is generated when the grid disk is created.

  • name: Unique name of the grid disk.

  • offset: Lowest byte offset of the grid disk on the physical disk.

  • size: Total size of the grid disk.

  • status: Current status of the grid disk, such as active, inactive, not present or importRequired.

Note:

The asmDeactivationOutcome and asmModeStatus attributes must be explicitly specified when using the LIST GRIDDISK command.

Example 8-82 Describing the GRIDDISK Object

This example shows the DESCRIBE command with the GRIDDISK object.

CellCLI> DESCRIBE GRIDDISK

         name                      modifiable
         asmDeactivationOutcome    hidden
         asmDiskgroupName   
         asmDiskName
         asmFailGroupName
         asmModeStatus             hidden
         availableTo               modifiable
         cachingPolicy             modifiable
         cellDisk
         comment                   modifiable
         creationTime
         diskType
         errorCount
         id
         offset
         size                      modifiable
         status

8.12.12 DESCRIBE IBPORT

Purpose

The DESCRIBE IBPORT command displays a list of attributes for the IBPORT object type.

Syntax

DESCRIBE IBPORT

Usage Notes

The following table lists the attributes for the DESCRIBE IBPORT command.

Table 8-10 DESCRIBE IBPORT Attributes

Attribute Description

activeSlave

Indicator whether the port is currently the active port for the bonded IP.

dataRate

The data rate of the InfiniBand port.

hcaFWVersion

The version of the host channel adapter firmware.

id

The Global unique identifier (GUID) of the InfiniBand port.

lid

The local identifier of the InfiniBand port. It is unique within the subnet, and the 16-bit identifiers are used within a network by switches for routing.

linkDowned

The number of times the port training state machine has failed the link error recovery process, and halted the link.

linkIntegrityErrs

The number of link integrity errors.

linkRecovers

The number of times the port training state machine has successfully completed the link error recovery process.

name

The name of the InfiniBand port.

physLinkState

The physical link state.

portNumber

The port number of the InfiniBand port.

rcvConstraintErrs

The number of received constraint errors experienced by the InfiniBand port.

rcvData

The number of 32-bit data words received by the InfiniBand port.

rcvErrs

The number of packets received at the InfiniBand port containing an error.

rcvRemotePhysErrs

The number of physical errors experienced at the InfiniBand port.

status

The link status.

symbolErrs

The number of minor link errors experienced at the InfiniBand port.

vl15Dropped

The number of incoming VL15 packets dropped at the InfiniBand port due to resource limitations, such as lack of buffers.

xmtConstraintErrs

The number of transmitted constraint errors experienced at the InfiniBand port.

xmtData

The number of 32-bit data words transmitted on the InfiniBand port.

xmtDiscards

The number of outbound packets discarded by the InfiniBand port because the port was down or congested.

Examples

The following example shows the DESCRIBE command with the IBPORT object.

Example 8-83 Describing the IBPORT Object

CellCLI> DESCRIBE IBPORT

        name
        activeSlave
        dataRate
        hcaFWVersion
        id
        lid
        linkDowned
        linkIntegrityErrs
        linkRecovers
        physLinkState
        portNumber
        rcvConstraintErrs
        rcvData
        rcvErrs
        rcvRemotePhysErrs
        status
        symbolErrs
        vl15Dropped
        xmtConstraintErrs
        xmtData
        xmtDiscards

8.12.13 DESCRIBE IORMPLAN

Purpose

The DESCRIBE IORMPLAN command displays a list of attributes for the IORMPLAN object type.

Syntax

DESCRIBE IORMPLAN

Usage Notes

The following table lists the attributes for the DESCRIBE IORMPLAN command.

Table 8-11 DESCRIBE IORMPLAN Attributes

Attribute Description

catPlan

Allocation plan for the categories set up in the databases using the cell.

dbPlan

Allocation plan for the databases using the cell.

name

Unique name of the interdatabase plan. The name value is automatically set to cellname_IORMPLAN.

objective

Optimization mode for IORM.

status

Current status of the interdatabase plan, either active or inactive.

Examples

The following example shows the DESCRIBE command with the IORMPLAN object.

Example 8-84 Describing the IORMPLAN Object

CellCLI> DESCRIBE IORMPLAN

         name
         catPlan                 modifiable
         dbPlan                  modifiable
         objective               modifiable
         status

Related Topics

8.12.14 DESCRIBE KEY

Purpose

The DESCRIBE KEY command displays a list of attributes for the KEY object type.

Syntax

DESCRIBE KEY

Usage Notes

The following table lists the attributes for the DESCRIBE KEY command.

Table 8-12 DESCRIBE KEY Attributes

Attribute Description

key

Random hexadecimal string used to assign client keys.

name

Name of the key. The value of this field is not displayed with LIST.

Examples

The following example shows the DESCRIBE command with the KEY object.

Example 8-85 Describing the KEY Object

CellCLI> DESCRIBE KEY

         name
         key                     modifiable

Related Topics

8.12.15 DESCRIBE LUN

Purpose

The DESCRIBE LUN command displays a list of attributes for the LUN object type.

Syntax

DESCRIBE LUN

Usage Notes

The following table lists the attributes for the DESCRIBE LUN command.

Table 8-13 DESCRIBE LUN Attributes

Attribute Description

cellDisk

This attribute is now obsolete.

deviceName

Operating system device name for the LUN. For example, /dev/c1d5

diskType

The type of disk.

errorCount

Number of errors on this LUN.

id

Identifier assigned by the system.

isSystemLun

Indicator whether the disk is a system disk. If value is TRUE, then the disk is a system disk. If the value is FALSE, then the disk is not a system disk, and only has data on it.

lunAutoCreate

Indicator whether the LUN was automatically created. Values are TRUE or FALSE. Single-disk LUNs are automatically created when disks without LUNs are converted to cell disks. For example, CREATE DISK ALL creates single-disk LUNs for all physical disks without LUNs. These single-disk LUNs have this attribute set to TRUE.

lunSize

Raw size of the LUN before being converted to a cell disk.

lunUID

Unique identifier assigned by the system.

lunWriteCacheMode

Status of LUN write cache. The status can be in Write Through Mode or Write Back Mode.

name

Unique name assigned to the LUN. This might be different (or extended from) the LUN ID if the ID is not unique.

overProvisioning

Indicator of the percentage of over-provisioned blocks in flash storage that are still available for a particular LUN. This attribute is only used for flash disks.

physicalDrives

Physical disk names that form the LUN.

raidLevel

Value of the RAID level that is used on the LUN. For example: RAID 0.

status

Status of the LUN, which can be normal, warning, or critical.

Examples

The following example shows the DESCRIBE command with the LUN object.

Example 8-86 Describing the LUN Object

CellCLI> DESCRIBE LUN

         name
         cellDisk
         deviceName
         diskType
         errorCount
         id
         lunAutoCreate
         isSystemLun
         lunSize
         lunUID
         lunWriteCacheMode
         overProvisioning
         physicalDrives
         raidLevel
         status

Related Topics

8.12.16 DESCRIBE METRICCURRENT

Purpose

The DESCRIBE METRICCURRENT command displays a list of attributes for the METRICCURRENT object type.

Syntax

DESCRIBE METRICCURRENT

Usage Notes

The following table lists the attributes for the DESCRIBE METRICCURRENT command.

Table 8-14 DESCRIBE METRICCURRENT Attributes

Attribute Description

alertState

Indicator of the alert state. Values are normal, warning, or critical.

collectionTime

Time stamp when the metric value was collected.

metricObjectName

Name of the object, such as cell disk, grid disk, and consumer group, being measured.

metricType

Specification for how the statistic was created or defined.

metricValue

Value of the metric when it was collected.

name

Unique name of the current metric.

objectType

Type of object being measured. Values are CELL, CELLDISK, FLASHCACHE, GRIDDISK, IORM_CATEGORY, IORM_DATABASE, IORM_CONSUMER_GROUP, or HOST_INTERCONNECT.

Examples

The following example shows the DESCRIBE command with the METRICCURRENT object.

Example 8-87 Describing the METRICCURRENT Object

CellCLI> DESCRIBE METRICCURRENT

         name
         alertState
         collectionTime
         metricObjectName
         metricType
         metricValue
         objectType

Related Topics

8.12.17 DESCRIBE METRICDEFINITION

Purpose

The DESCRIBE METRICDEFINITION command displays a list of attributes for the METRICDEFINITION object type.

Syntax

DESCRIBE METRICDEFINITION

Usage Notes

The following table lists the attributes for the DESCRIBE METRICDEFINITION command.

Table 8-15 DESCRIBE METRICDEFINITION Attributes

Attribute Description

description

Description of the metric.

metricType

Indicator of how the statistic was created or defined. The options are as follows:

  • cumulative: Cumulative statistics since the metric was created.

  • instantaneous: Value at the time that the metric is collected.

  • rate: Rates computed by averaging statistics over observation periods.

  • transition: Transition metrics are collected at the time their value has changed and typically capture important transitions in hardware status.

name

Unique name of the metric definition. The value of the name attribute is a composite of abbreviations. The attribute value starts with an abbreviation of the object type on which the metric is defined:

  • CL_ (cell)

  • CD_ (cell disk)

  • GD_ (grid disk)

  • FC_ (flash cache)

  • DB_ (database-level)

  • CG_ (consumer group, database-qualified)

  • CT_ (category)

  • N_ (network)

After the abbreviation of the object type, most of the name attributes contain one of the following combinations to identify the operation:

  • IO_RQ (number of requests)

  • IO_BY (number of MB)

  • IO_TM (I/O latency)

  • IO_WT (I/O wait time)

Next, in the name could be _R or _W for read or write. Following that in the name attribute value there might be _SM or _LG to identify small or large blocks, respectively. At the end of the name, there could be _SEC to signify per seconds or _RQ to signify per request.

For consumer group and category metrics, read or write details are omitted.

For example:

  • CD_IO_RQ_R_SM is the number of requests to read small blocks on a cell disk.

  • GD_IO_TM_W_LG is the microseconds of I/O latency writing large blocks on a grid disk.

objectType

Options are CELL, CELLDISK, CELL_FILESYSTEM, GRIDDISK, IORM_CATEGORY, IORM_DATABASE, IORM_CONSUMER_GROUP, or HOST_INTERCONNECT.

persistencePolicy

Amount of time metric values are stored.

unit

Unit for the metric explicitly, and is related to the metric collected:

  • Number

  • % (percentage)

  • F (Fahrenheit)

  • C (Celsius)

Examples

The following example shows the DESCRIBE command with the METRICDEFINITION object.

Example 8-88 Describing the METRICDEFINITION Object

CellCLI> DESCRIBE METRICDEFINITION

         name
         description
         metricType
         objectType
         persistencePolicy
         unit

8.12.18 DESCRIBE METRICHISTORY

Purpose

The DESCRIBE METRICHISTORY command displays a list of attributes for the METRICHISTORY object type.

Syntax

DESCRIBE METRICHISTORY

Usage Notes

The following table lists the attributes for the DESCRIBE METRICHISTORY command.

Table 8-16 DESCRIBE METRICHISTORY Attributes

Attribute Description

alertState

Indicator of the alert state. Values are normal, warning, or critical.

collectionTime

Time stamp when the metric value was collected.

memory

The metrics in Management Server memory. This attribute can be used instead of the collectionTime attribute when the collection time is less than an hour.

metricObjectName

Name of the object, such as cell disk, grid disk, and consumer group, being measured.

metricType

Specification for how the statistic was created or defined.

metricValue

Value of the metric when it was collected.

metricValueAvg

Average value of the metric.

metricValueMax

Maximum value of the metric.

metricValueMin

Minimum value of the metric.

name

Unique name of the current metric.

objectType

Type of object being measured. Values are CELL, CELLDISK, GRIDDISK, IORM_CATEGORY, IORM_DATABASE, IORM_CONSUMER_GROUP, or HOST_INTERCONNECT.

over

Specification for amount of time in minutes for the aggregation. This attribute works in conjunction with the max, min and avg keywords.

Examples

The following example shows the DESCRIBE command with the METRICHISTORY object.

Example 8-89 Describing the METRICHISTORY Object

CellCLI> DESCRIBE METRICHISTORY

         name
         alertState
         collectionTime
         memory
         metricObjectName
         metricType
         metricValue
         metricValueAvg
         metricValueMax
         metricValueMin
         objectType
         over

8.12.19 DESCRIBE PHYSICALDISK

Purpose

The DESCRIBE PHYSICALDISK command displays a list of attributes for the PHYSICALDISK object type.

Syntax

DESCRIBE PHYSICALDISK

Usage Notes

The following table lists the attributes for the DESCRIBE PHYSICALDISK command.

Table 8-17 DESCRIBE PHYSICALDISK Attributes

Attribute Description

diskType

Type of the disk, whether it is a HARDDISK or a FLASHDISK.

enclosureDeviceId

Identifier for the hard disk enclosure. This attribute is only applicable to Oracle Exadata Storage Server Software on Oracle Exadata Storage Server.

luns

List of LUNs converted from this disk.

makeModel

Model description provided by the system.

name

Unique name of the physical disk.

physicalInsertTime

Time that the disk was inserted.

physicalInterface

Interface type used by the hard disk. For example, SAS

physicalSerial

System-assigned unique ID.

physicalSize

Size of the disk in bytes.

physicalUseType

Intended use of the disk. For example, Data Drive.

slotNumber

Physical location of disk. This attribute is only applicable to Oracle Exadata Storage Server Software on Oracle Exadata Storage Server.

status

Status of the physical disk. Values can be as follows:

  • failed: disk has failed. In earlier releases, this status was called critical.

  • normal: disk is functioning normally

  • not present: disk has been removed

  • peer failure: flash disk failure only

  • poor performance: disk is performing poorly

  • predictive failure: disk is expected to fail

  • write-through caching: flash disk caching only.

Examples

Example 8-90 Describing the PHYSICALDISK Object on a Hard Drive in Oracle Exadata Storage Server

cellcli> DESCRIBE PHYSICALDISK

         name
         diskType
         enclosureDeviceId
         luns
         makeModel
         physicalInsertTime
         physicalInterface
         physicalSerial
         physicalSize
         slotNumber
         status

Example 8-91 Describing the PHYSICALDISK Object on a Flash Drive in Oracle Exadata Storage Server

cellcli> DESCRIBE PHYSICALDISK

         name
         diskType
         luns
         makeModel
         physicalInsertTime
         physicalSerial
         physicalSize
         slotNumber
         status

8.12.20 DESCRIBE QUARANTINE

Purpose

The DESCRIBE QUARANTINE command displays a list of quarantines.

Syntax

DESCRIBE QUARANTINE

Usage Notes

The following table lists the attributes for the DESCRIBE QUARANTINE command.

Table 8-18 DESCRIBE QUARANTINE Attributes

Attribute Description

name

Identifier of the quarantine.

asmClusterId

Identifier of the ASM cluster. This attribute is available in Exadata software 12.2.1.1.0 and later.

catDBPlan

The name of the category plan.

cellsrvChecksum

Checksum of the CELLSRV binary.

clientPID

The process identifier for the client process which crashed the cell.

comment

Comment for the quarantine.

conDbUniqueID

The container database unique ID for the quarantine

conDbUniqueName

The container database unique name for the quarantine.

crashReason

Reason for the crash.

creationTime

Quarantine creation time.

dbUniqueID

The database unique ID for the quarantine.

dbUniqueName

The database unique name for the quarantine.

fineGrainControl

 

fineGrainValue

 

incidentID

The incident identifier of the crash that caused the quarantine creation.

interDBPlan

The name of the interdatabase resource plan.

intraDBPlan

The name of the intradatabase resource plan.

ioBytes

The bytes of quarantined disk region. This is applicable to disk region quarantine only.

ioGridDisk

The grid disk name for quarantined disk region. This is applicable to disk region quarantine only.

ioOffset

The I/O offset for quarantined disk region. This is applicable to disk region quarantine only.

objectID

 

planLineID

The SQL Plan Line identifier. This is applicable to SQL Plan quarantine only.

quarantineMode

 

quarantinePlan

This is usually SYSTEM.

quarantineReason

The reason for creation of the quarantine.

quarantineType

The type of quarantine created.

remoteHostName

The host name of the remote host that ran the client process that crashed the cell.

rpmVersion

The RPM version of the cell being used when the cell crashed.

sqlID

The SQLID of the SQL statement that crashed a cell.

sqlPlanHashValue

The SQL Plan hash value. This is applicable to SQL Plan quarantine only.

Examples

Example 8-92 shows the DESCRIBE command with the QUARANTINE object.

Example 8-92 Describing the QUARANTINE Object

CellCLI> DESCRIBE QUARANTINE
         name
         cellsrvChecksum
         clientPID
         comment                 modifiable
         crashReason
         creationTime
         dbUniqueID
         dbUniqueName
         incidentID
         ioBytes
         ioGridDisk
         ioOffset
         planLineID
         quarantineReason
         quarantineType
         remoteHostName
         rpmVersion
         sqlID
         sqlPlanHashValue

8.12.21 DESCRIBE ROLE

Purpose

The DESCRIBE ROLE command displays a list of attributes for the ROLE object type.

Syntax

DESCRIBE ROLE

Usage Notes

The following table lists the attributes for the DESCRIBE ROLE command.

Table 8-19 DESCRIBE ROLE Attributes

Attribute Description

name

Unique name of the user assigned the role.

privileges

Privileges granted to the role.

Examples

The following example shows the DESCRIBE command with the ROLE object.

Example 8-93 Describing the ROLE Object

CellCLI> DESCRIBE ROLE

         name
         privilege                 modifiable

8.12.22 DESCRIBE THRESHOLD

Purpose

The DESCRIBE THRESHOLD command displays a list of attributes for the THRESHOLD object type.

Syntax

DESCRIBE THRESHOLD

Usage Notes

The following table lists the attributes for the DESCRIBE THRESHOLD command.

Table 8-20 DESCRIBE THRESHOLD Attributes

Attribute Description

comparison

Operator for comparing the metric value to the threshold value (>, >=, =, <, <=) to determine whether the value violates the threshold.

critical

Limit beyond which the metric value is considered to be in the critical state for generating alerts.

name

Unique name of the threshold.

observation

Number of measurements over which the rate metric is averaged before being compared with the threshold value.

occurrences

Number of consecutive violations of the threshold limit by the metric value before the appropriate alert is issued.

warning

Limit beyond which the metric value is considered to be in the warning state for generating alerts.

Examples

The following example shows the DESCRIBE command with the THRESHOLD object.

Example 8-94 Describing the THRESHOLD Object

CellCLI> DESCRIBE THRESHOLD

         name
         comparison              modifiable
         critical                modifiable
         observation             modifiable
         occurrences             modifiable
         warning                 modifiable

8.12.23 DESCRIBE USER

Purpose

The DESCRIBE USER command displays a list of attributes for the USER object type.

Syntax

DESCRIBE USER

Usage Notes

The following table lists the attributes for the DESCRIBE USER command.

Table 8-21 DESCRIBE ROLE Attributes

Attribute Description

name

Unique name of the user.

roles

Roles assigned to the user.

Examples

The following example shows the DESCRIBE command with the USER object.

Example 8-95 Describing the USER Object

CellCLI> DESCRIBE USER

         name
         roles

8.13 DROP

Purpose

The DROP command removes the named objects from the cell or resets a cell.

Syntax

DROP object_type [object_name [, object_name]...] [options]

Usage Notes

  • object_type can be one of the following:

    • ALERTHISTORY

    • CELL

    • CELLDISK

    • FLASHCACHE

    • FLASHLOG

    • GRIDDISK

    • QUARANTINE

    • ROLE

    • SOFTWAREHISTORY

    • THRESHOLD

    • USER

  • object_name is the name of a cell disk, grid disk, role, threshold, or user.

  • When multiple objects are the target of a DROP command, there is the possibility of partial success. If an error occurs, then the command is interrupted, and the remaining objects are not dropped.

8.13.1 DROP ALERTHISTORY

Purpose

The DROP ALERTHISTORY command removes alerts from the alert history of a cell.

Syntax

DROP ALERTHISTORY {ALL | alert1 {, alert2}, ...}

Usage Notes

  • In the command, alertN is the name of the alert to be dropped from the history.

  • When dropping stateful alerts, you must drop all members of the alert sequence at the same time. If you do not drop all members, then an error is issued by the system.

Examples

The following example shows the DROP ALERTHISTORY command.

Example 8-96 Dropping a Cell Alert History

CellCLI> DROP ALERTHISTORY 1, 2_1, 2_2

8.13.2 DROP CELL

Purpose

The DROP CELL command resets a cell to its original state.

Syntax

DROP CELL [ERASE = value] [FORCE] 

Usage Notes

  • This command is run from within the cell.

  • All cell disks, grid disks, and thresholds are dropped. The interdatabase plan is reset to its default state. All cell attributes are set to default values.

  • The FORCE option is required if the grid disks are configured on any cell disks when DROP CELL is issued. Otherwise, an error is reported.

  • The ERASE option erases the content on the disk by overwriting the content. The values are as follows:

    • 1pass: One pass, and the content is overwritten with zeros. This value is not available for flash drives.

    • 3pass: Three passes, and the content is overwritten with set data patterns. This option follows the recommendations of NNSA. This value is not available for flash drives.

    • 7pass: Seven passes, and the disk is overwritten with set data patterns. This option follows the recommendations from DOD.

  • Flash cache compression must be disabled before securely erasing a drive.

  • When dropping all cells using the 1pass or 3pass option, it necessary to drop the flash disks first using the 7pass option, and then drop the cells. The following is an example of the commands:

    CellCLI> DROP CELLDISK ALL FLASHDISK ERASE=7pass 
    CellCLI> DROP CELL ERASE=1pass 
    

The following table shows approximate time needed to securely erase a drive using the supported algorithms. When multiple grid disks or cell disks are dropped with the ERASE option, the command runs in parallel on all disks and flash drives. However, the recommended method of erasing data from a cell is to use Secure Erase. See Securely Erasing Database Servers and Storage Servers in Oracle Exadata Database Machine Security Guide.

Type of Drive 1pass 3pass 7pass

600 GB drive

1 hour

3 hours

7 hours

1.2 TB drive

1.67 hours

5 hours

11.67 hours

2 TB drive

5 hours

15 hours

35 hours

3 TB drive

7 hours

21 hours

49 hours

4 TB drive

8 hours

24 hours

56 hours

8 TB drive

13.17 hours

39.5 hours

92.17 hours

10 TB drive

14 hours

42 hours

98 hours

22.875 GB flash drive

NA

NA

21 minutes

93 GB flash drive

NA

NA

32 minutes

186 GB flash drive

NA

NA

36 minutes

1.6 TB flash drive

NA

NA

5.5 hours

3.2 TB flash drive

NA

NA

8 hours

Example 8-97 Dropping a Cell

CellCLI> DROP CELL FORCE

Related Topics

8.13.3 DROP CELLDISK

Purpose

The DROP CELLDISK command removes all or the named cell disks from the cell.

This command is necessary if a cell disk fails, or it is replaced by a newer model.

Before dropping the cell disk, you should drop its grid disks and the corresponding Oracle ASM disks from the disk groups. The Oracle ASM disks should be dropped before dropping the grid disks.

Syntax

DROP CELLDISK { ALL [FLASHDISK | HARDDISK] | cdisk_name [, cdisk_name]... }
              [ERASE = value [NOWAIT]] [FORCE] 

Usage Notes

  • If individual cell disks are specified, then the named cell disks (cdisk_name) are dropped.

  • If the LUN associated with the CELLDISK is flagged as automatically created, then that LUN is deleted along with the cell disk.

  • If the ALL option is specified, then all the cell disks on the cell are removed.

  • The FLASHDISK option limits the DROP CELLDISK command to cell disks that are flash disks.

  • The HARDDISK option limits the DROP CELLDISK command to cell disks that are hard disks.

  • If grid disks are configured on the cell disk when DROP CELLDISK is issued, then the FORCE option must be used or an error is reported. The FORCE option causes any grid disks to be dropped first, and then the cell disk is dropped.

  • If the specified cell disk includes flash cache, and that flash cache is in writeback mode, then the cell disk cannot be dropped.

  • The ERASE option erases the content on the disk by overwriting the content. The values are as follows:

    • 1pass: One pass, and the content is overwritten with zeros. This option is not applicable for flash drives. This value is not available for flash drives.

    • 3pass: Three passes, and the content is overwritten with set data patterns. This option follows the recommendations from NNSA. This option is not applicable for flash drives. This value is not available for flash drives.

    • 7pass: Seven passes, and the disk is overwritten with set data patterns. This option follows the recommendations from DOD.

  • When dropping all cell disks using the 1pass or 3pass option, it necessary to drop the flash disks first using the 7pass option, and then drop the cell disks. The following is an example of the commands:

    CellCLI> DROP CELLDISK ALL FLASHDISK ERASE=7pass 
    CellCLI> DROP CELLDISK ALL ERASE=1pass 
    
  • Use the NOWAIT option with the ERASE option to run the command asynchronously.

Example 8-98 Examples of Dropping a Cell Disk

CellCLI> DROP CELLDISK CD_03_cell01

CellCLI> DROP CELLDISK CD_02_cell06 FORCE

CellCLI> DROP CELLDISK ALL

CellCLI> DROP CELLDISK CD_02_cell09 ERASE=1pass NOWAIT
CellDisk CD_02_cell09 erase is in progress 

Related Topics

8.13.4 DROP FLASHCACHE

Purpose

The DROP FLASHCACHE command removes Exadata Smart Flash Cache from a cell.

Syntax

DROP FLASHCACHE

Usage Notes

Before dropping flash cache, the data not synchronized with the grid disk (dirty data) must be flushed from flash cache to the grid disks. Not flushing dirty data may cause data loss.

Examples

The following example shows how to remove Exadata Smart Flash Cache from a cell.

Example 8-99 Removing Exadata Smart Flash Cache

CellCLI> DROP FLASHCACHE

Related Topics

8.13.5 DROP FLASHLOG

Purpose

The DROP FLASHLOG command removes Oracle Exadata Smart Flash Log from a cell.

Syntax

DROP FLASHLOG [FORCE]

Usage Notes

The DROP FLASHLOG command can be run at runtime, but the command does not complete until all redo data on the flash disk is written to hard disk.

If FORCE is not specified, then the DROP FLASHLOG command fails if there is any saved redo. If FORCE is specified, then all saved redo is purged, and Oracle Exadata Smart Flash Log is removed.

Caution:

If DROP FLASHLOG fails due to the existence of saved redo, then do not use the FORCE option unless you are sure that all saved redo is no longer needed for any databases to perform recovery. Contact Oracle Support Services for additional information.

Examples

The following example shows how to remove Exadata Smart Flash Cache from a cell.

Example 8-100 Removing Oracle Exadata Smart Flash Log from a Cell

CellCLI> DROP FLASHLOG

CellCLI> DROP FLASHLOG FORCE

8.13.6 DROP GRIDDISK

Purpose

The DROP GRIDDISK command removes the named grid disks from the cell or removes all the grid disks specified by the ALL PREFIX option.

Caution:

Before dropping a grid disk that belongs to an Oracle ASM disk group, ensure that the corresponding disk was dropped from the Oracle ASM disk group.

Syntax

DROP GRIDDISK {ALL [FLASHDISK | HARDDISK ] PREFIX=gdisk_name_prefix , | gdisk_name 
              [, gdisk_name]... } [ERASE = value [NOWAIT]]  [FORCE]

Usage Notes

  • If the gdisk_name is entered, then the name identifies the individual grid disk to be removed. Multiple names can be entered.

  • If the ALL PREFIX option is entered, then the gdisk_name_prefix option specifies the prefix assigned to the names of the grid disks to be dropped. The PREFIX option is required when ALL is used.

    Note:

    A comma must be entered after the grid disk prefix when it is followed by the ERASE option.

  • The FLASHDISK option limits the DROP GRIDDISK command to grid disks that are flash disks.

  • The HARDDISK option limits the DROP GRIDDISK command to grid disks that are hard disks.

  • If any of the grid disks are in use when DROP GRIDDISK is issued, then an error is reported. You can use ALTER GRIDDISK with the INACTIVE option to deactivate a grid disk before dropping the grid disk. This action ensures that the grid disk is not in use.

  • The FORCE option can be used to force the drop of a grid disk that is in use.

  • If the grid disk being dropped was created on a cell disk of type FLASHDISK, then it does not re-create that area or any part of that grid disk or cell disk as FLASHCACHE automatically. Use the CREATE FLASHCACHE command to reuse any part of the dropped area for FLASHCACHE.

  • The ERASE option erases the content on the disk by overwriting the content. The values are as follows:

    • 1pass: One pass, and the content is overwritten with zeros. This option is not applicable for flash drives. This value is not available for flash drives.

    • 3pass: Three passes, and the content is overwritten with set data patterns. This option follows the recommendations from NNSA. This option is not applicable for flash drives. This value is not available for flash drives.

    • 7pass: Seven passes, and the disk is overwritten with set data patterns. This option follows the recommendations from DOD.

  • When dropping all grid disks using the 1pass or 3pass option, it necessary to drop the flash disks first using the 7pass option, and then drop the grid disks. The following is an example of the commands:

    CellCLI> DROP GRIDDISK ALL FLASHDISK PREFIX=data, ERASE=7pass 
    CellCLI> DROP GRIDDISK ALL PREFIX=data, ERASE=1pass 
    
  • Use the NOWAIT option with the ERASE option to run the command asynchronously.

Example 8-101 Examples of Dropping a Grid Disk

CellCLI> ALTER GRIDDISK data01_CD_03_cell01 INACTIVE

CellCLI> DROP GRIDDISK data01_CD_03_cell01

CellCLI> DROP GRIDDISK ALL PREFIX=data01

CellCLI> DROP GRIDDISK data02_CD_04_cell01 FORCE

CellCLI> DROP GRIDDISK data02_CD_04_cell01 ERASE=1pass
GridDisk data02_CD_04_cell01 successfully dropped 

CellCLI> DROP GRIDDISK ALL FLASHDISK PREFIX=DATA, ERASE=7pass
CellCLI> DROP GRIDDISK ALL PREFIX=DATA, ERASE=3pass 

8.13.7 DROP QUARANTINE

Purpose

The DROP QUARANTINE command manually drops a quarantine.

Syntax

DROP QUARANTINE { ALL | quarantine1 [, quarantine2]... }  

Usage Notes

In general, a quarantine can be removed if the quarantined entity is not expected to cause more problem to CELLSRV. For example, cell offload for problem SQL statements is disabled, or an Oracle Database patch is applied. Refer to the alert message for the quarantine for more details.

When a cell is patched, all quarantines are automatically dropped. It is not necessary to drop them manually.

Examples

The following example shows the DROP QUARANTINE command.

Example 8-102 Dropping Quarantines

CellCLI> DROP QUARANTINE 1

8.13.8 DROP ROLE

Purpose

The DROP ROLE command removes user roles from the cell.

Syntax

DROP ROLE  { ALL | role_name1 [, role_name2, ...]} [FORCE]

Usage Notes

The FORCE option drops the role when the role has been granted to a user.

Examples

The following example shows how to drop a role.

Example 8-103 Dropping a Role

CellCLI>DROP ROLE gd_monitor

8.13.9 DROP SOFTWAREHISTORY

Purpose

The DROP SOFTWAREHISTORY command removes all history or individual update history.

Syntax

DROP SOFTWAREHISTORY { ALL | 'update_name[,update_name...]'}

Example 8-104 Dropping the History of Scheduled Software Updates

CellCLI> DROP SOFTWAREHISTORY '12.2.1.2.0.170509,12.2.1.2.0.17052'

CellCLI> DROP SOFTWAREHISTORY ALL

8.13.10 DROP THRESHOLD

Purpose

The DROP THRESHOLD command removes all or the specified thresholds from the cell.

Syntax

DROP THRESHOLD { ALL |threshold_name [, threshold_name ...] }

Examples

The following example shows the DROP THRESHOLD command.

Example 8-105 Dropping Thresholds

CellCLI> DROP THRESHOLD ct_io_wt_rq.interactive

CellCLI> DROP THRESHOLD ALL

Related Topics

8.13.11 DROP USER

Purpose

The DROP USER command removes a user from a cell.

Syntax

DROP USER { ALL | user1 [, user2]... }

Examples

The following example shows how to drop a user.

Example 8-106 Dropping a User

CellCLI>DROP USER agarcia

8.14 EXIT

Purpose

The EXIT command exits from the CellCLI utility, and returns control to the operating system prompt.

Syntax

EXIT

EXIT has the same functionality as the QUIT command.

8.15 EXPORT CELLDISK

Purpose

The EXPORT CELLDISK command prepares all cell disks or a specified cell disk before moving (importing) the cell disk to a different cell.

Syntax

EXPORT CELLDISK { ALL | cdisk_name }

Usage Notes

To move a cell disk from one cell to another, use the EXPORT CELLDISK and IMPORT CELLDISK commands. Usually, all disks are moved to a new cell if the current cell is failing. First, export the cell disk on one cell. Then, import the exported cell disk using the CellCLI utility on the cell where you moved the physical drive that contains the cell disk.

When the EXPORT CELLDISK command is run:

  • ALL exports all cell disks on the cells that have normal status.

  • If the LUN associated with the cell disk is flagged as automatically-created, then that LUN is deleted as part of the export.

  • A successfully exported cell disk has the status attribute set to ImportRequired, and the exported cell disk is displayed in the output of the LIST CELLDISK command.

  • The following apply when a cell disk is exported (status='ImportRequired') before it is imported:

    • You can change the name and comment attributes.

    • You can drop the cell disk.

    • You cannot create a new grid disk on the cell disk.

  • When a disk is exported, any writes from the disk controller cache to the disk are cleared, and the disk is flagged to indicate that the disk was exported. The grid disks on the disk are no longer visible to Oracle ASM. Any I/Os to the grid disks get errors.

Before exporting a cell disk, the data not synchronized with the grid disk (dirty data) must be flushed from flash cache to the grid disks. Not flushing dirty data may cause data loss.

Examples

The following example shows the EXPORT CELLDISK command.

Example 8-107 Exporting a Cell Disk

CellCLI> EXPORT CELLDISK CD_3_cell01

CellCLI> EXPORT CELLDISK ALL

Related Topics

8.16 GRANT

Purpose

The GRANT command sets attributes for privileges and roles.

Syntax

GRANT object_type [name] TO sub_object_type [sub_object_name]
   

Usage Notes

  • object_type can be as follows:

    • PRIVILEGE

    • ROLE

  • The following can be used for PRIVILEGE object type:

    • name is in the following format:

      { ALL ACTIONS | action } ON { ALL OBJECTS | object }               \
      [{ ALL ATTRIBUTES | ATTRIBUTES attribute1 [, attribute2, ...] }]   \
      [{ WITH ALL OPTIONS | WITH OPTIONS option1 [, option2, ...] }]
      
    • The sub_object_type must be ROLE.

    • The sub_object_name is the name of the role.

  • The following can be used for the ROLE object type:

    • name is the role name.

    • The sub_object_type must be USER.

    • The sub_object_name is the name of the user.

Related Topics

8.16.1 GRANT PRIVILEGE

Purpose

The GRANT PRIVILEGE command sets the cell access privileges for a role.

Syntax

GRANT PRIVILEGE { ALL ACTIONS | action } ON { ALL OBJECTS | object }   \
{ ALL ATTRIBUTES | ATTRIBUTES attribute1 [, attribute2, ...] }         \
{ WITH ALL OPTIONS | WITH OPTIONS option1 [, option2, ...] }           \
TO ROLE { ALL | role1 [, role2, ...] }

Usage Notes

  • action is the command. Examples: alter, create, describe, drop, export, import, list.

    Notes:

    • The grant and revoke commands cannot be granted.

    • create user and drop user cannot be granted.

    • create role and drop role cannot be granted.

  • object is object type for the action. It can be any CellCLI object. Examples: cell, celldisk, flashcache, flashlog, griddisk, role.

  • attribute are the attributes for the object. To get a list of attributes for an object, run the LISTobjecttype command.

  • option are the options for the object. Examples: DETAIL, LIMIT, ORDER BY, WHERE.

  • role is the name of the role to grant privileges.

  • The ALL ACTIONS argument grants privileges for all actions.

  • The ALL OBJECTS argument grants privileges for all objects.

  • The ALL ATTRIBUTES argument grants privileges for all attributes.

  • The WITH ALL OPTIONS argument grants privileges for all options.

  • Specifying attributes and WITH OPTIONS is optional. If they are not specified, then all attributes and options are granted with the privilege.

Examples

Example 8-108 Granting Privileges to a Role

This example shows how to grant privileges to a role.

CellCLI> GRANT PRIVILEGE list on griddisk ATTRIBUTES name,size  \
         WITH OPTIONS detail TO ROLE gd_monitor

Example 8-109 Granting All Attributes and Options to a Role

This example shows how to grant all attributes and options for a specified action and object to a role.

CellCLI> GRANT PRIVILEGE { ALL ACTIONS | action } ON { ALL OBJECTS | object } to ROLE r1

Example 8-110 Granting All Options with Specified Action, Object and Attributes

This example shows how to grant all options with a specified action, object and attributes to a role.

CellCLI> GRANT PRIVILEGE { ALL ACTIONS | action } ON { ALL OBJECTS | object }  \
ATTRIBUTES <attribute1> [, attribute2, ...] to ROLE r1

Example 8-111 Granting All Attributes with Specified Action, Object and Options

This example shows how to grant all attributes with a specified action, object, and options to a role.

CellCLI> GRANT PRIVILEGE { ALL ACTIONS | action } ON { ALL OBJECTS | object }   \
WITH OPTIONS <option1> [, option2, ...] to ROLE r1

8.16.2 GRANT ROLE

Purpose

The GRANT ROLE command sets the role for a user.

Syntax

GRANT ROLE { ALL | role1 [, role2, ...] } TO USER { ALL | user1 [, user2...] }

Usage Notes

  • role is the name of the role.

  • The ALL argument grants all roles to the user.

  • The TO USER ALL argument grants the role to all users.

Examples

Example 8-112 Granting a Role to a User

This example shows how to grant a role to a user.

CellCLI> GRANT ROLE gd_monitor TO USER agarcia

8.17 HELP

Purpose

The HELP command displays syntax and usage descriptions for all CellCLI commands.

Syntax

HELP [help_topic]

If no topic argument is provided, HELP displays the name of all available topics. If a topic is specified, then detailed help text is displayed for that topic.

The following example shows examples of the HELP command.

Example 8-113 Display Help Text with the HELP Command

CellCLI> HELP
CellCLI> HELP ALTER
CellCLI> HELP ALTER CELL

8.18 IMPORT CELLDISK

Purpose

The IMPORT CELLDISK command reinstates all exported cell disks or an exported cell disk on a cell where you moved the physical drives that contain the cell disks.

The cell disk is typically imported to a different cell than the one from which the cell disk was exported. For example, the physical drive that contains the exported cell disk was moved to a different cell.

When you move a disk with cell disks and grid disks on it from one machine to another, be careful to ensure that the data on it is rebalanced, as per the ASM failure groups. If all disks from one cell are moved to another cell, then there is no need to perform a ASM rebalance, since the entire failure group is moved.

Syntax

IMPORT CELLDISK  { ALL  |  cdisk_name  LUN=lun_id  | cdisk_name |  LUN=lun_id }
    [, comment=comment_text] [FORCE]

Usage Notes

To move a cell disk from one cell to another, use the EXPORT CELLDISK and IMPORT CELLDISK commands. Usually, all disks are moved to a new cell if the current cell is failing. First, export the cell disk on one cell. Then, import the exported cell disk using the CellCLI utility on the cell where you moved the physical drive that contains the cell disk.

When the IMPORT CELLDISK command is run:

  • Either ALL, the cell disk name, the LUN ID, or the cell disk name and LUN ID must be specified.

    • ALL imports cell disks that have ImportRequired status.

    • If the cell disk name is provided and the LUN ID is not provided, then you can import a cell disk by the specified name in cases where Management Server recognizes this cell disk. A recognized cell disk is displayed in the output of LIST CELLDISK with status equal to ImportRequired.

    • If the LUN ID is provided and the cell disk name is not provided, then the LUN is scanned, and the cell disk is imported. This variation of the command can be used to import a newly-inserted cell disk that was not recognized by Management Server and Cell Server.

    • If the LUN ID and cell disk name are both provided, then the LUN ID is used to import the cell disk, and the name is used to rename the imported cell disk.

  • A new value can be entered for the comment attribute to update the existing cell disk comment.

  • The cell disk name is verified to ensure that the name is unique within the cell. Cell disks can be renamed before import to ensure uniqueness.

  • The grid disk names within a cell must be unique. If a physical disk is moved from one cell (cell_A) to another cell (cell_B) using the EXPORT and IMPORT commands, then there is a chance that the target cell (cell_B) could have two grid disks with identical names. In this case, the cell software automatically resolves the naming conflict by adding a temporary suffix (_duplicate_name, _duplicate_name2, _duplicate_name3, and so on) to the name of one of the grid disks. This additional suffix enables you to refer to a grid disk unambiguously in the CellCLI commands.

    It is recommended that you rename a duplicate grid disk on a cell (cell_B) with a new permanent unique name using the following command:

    ALTER GRIDDISK gdname_duplicate_name NAME=new_unique_name
    

    If you return the physical disk to the original cell (cell_A) or move the disk to another cell rather than renaming the disk, then the grid disk displays its original name.

  • The LIST CELLDISK command shows which cell disks need to be imported. The command displays output similar to the following:

    CellCLI> list celldisk
             CD_01_cell00     normal
             CD_01_cell01     normal
             CD_01_cell02     importRequired
             CD_01_cell03     importForceRequired
             CD_01_cell04     importRequired
             CD_01_flash0     normal
             CD_01_flash1     normal
             CD_01_flash2     normal
             CD_01_log00      normal
             CD_01_log01      normal
    
  • If the cell disk was not successfully exported and moved between cells, then the FORCE option must be specified with IMPORT or an error occurs.Oracle recommends contacting Oracle Support Services before using the FORCE option.

  • The IMPORT command checks the disk to determine if it was exported. If it was exported, then the IMPORT command makes the grid disk visible to Oracle ASM. If the disk was not exported, then the FORCE option should be used with the IMPORT command to reconstruct the grid disks on the disk, and make them visible to Oracle ASM.

Example 8-114 Importing a Cell Disk

This example shows the IMPORT CELLDISK command. The LUN ID is provided with the IMPORT command to identify the cell disk, and the cell disk name is used to rename the cell disk on the cell where it was imported.

CellCLI> IMPORT CELLDISK CD_7_cell04 lun=3

CellCLI> IMPORT CELLDISK ALL

8.19 LIST

Purpose

The LIST command displays attributes for Oracle Exadata Storage Server Software objects. Objects displayed are identified by name or by filters. The attributes displayed for each object are determined by the specified attribute list.

Syntax

LIST object_type  [ name | attribute_filters] [attribute_list] [DETAIL]  \
[ORDER BY attribute [ASC| DESC][, attribute [ASC| DESC], ...] \
[LIMIT integer]

Usage Notes

  • object_type can be the following:

    • ACTIVEREQUEST

    • ALERTDEFINITION

    • ALERTHISTORY

    • CELL

    • CELLDISK

    • DATABASE

    • DISKMAP

    • FLASHCACHE

    • FLASHCACHECONTENT

    • FLASHLOG

    • GRIDDISK

    • IBPORT

    • IORMPLAN

    • IORMPROFILE

    • KEY

    • LUN

    • METRICCURRRENT

    • METRICDEFINITION

    • METRICHISTORY

    • OFFLOADGROUP

    • PHYSICALDISK

    • PLUGGABLEDATABASE

    • QUARANTINE

    • ROLE

    • THRESHOLD

    • SOFTWAREHISTORY

    • SOFTWAREUPDATE

    • USER

  • Using LIST with only an object_type (without the DETAIL option or an attribute list) displays the names of the existing objects of this type and a default list of attributes.

    • For an object type that has a status attribute, the object name and the status are displayed.

    • For the METRICHISTORY object type, the collection time, the object name, and value are displayed.

    • For the PHYSICALDISK and LUN object types, the ID attribute is displayed.

    • For the ALERTHISTORY object type, the time and alert message are displayed.

    • For the KEY object type, the key value is displayed.

  • The attributes displayed for each object are determined by the specified attribute list. Attribute values that are strings with embedded blank spaces or tabs must be enclosed in quotation marks.

  • Attribute filters determine the specific objects that are displayed. Because of the amount of metrics, you should use filters when using the LIST METRICCURRENT or LIST METRICHISTORY commands to narrow the output of the command.

  • In the default format without the DETAIL option, each object is displayed on a separate line, with successive attribute values separated by tabs in the order of the specified list of attributes.

  • In the DETAIL format, each attribute of a specific object is displayed on a separate line, with an attribute name followed by its value. If no attribute list is provided, then all attributes that have values are displayed. Blank lines separate each object in the display. DETAIL is similar to the ATTRIBUTES ALL option, only the format is different.

  • Attributes that are not set are not listed with the DETAIL option. However, attributes that are set to an empty value are listed with the DETAIL option.

  • The ORDER BY option orders attributes in ascending or descending order. The default is ASC.

  • The LIMIT option sets a limit on the number of displayed attributes. The maximum value is 100 when LIMIT is used with the ORDER BY option.

8.19.1 LIST ACTIVEREQUEST

Purpose

The LIST ACTIVEREQUEST command displays specified attributes for the outstanding active requests for the cell.

Syntax

LIST ACTIVEREQUEST  [ name |  attribute_filters ]  [attribute_list] [DETAIL]

Usage Notes

The list of attributes that can be displayed is shown in the following example.

Example 8-115 Listing ACTIVEREQUEST Attributes

This example shows the LIST command with the ACTIVEREQUEST object.

CellCLI> LIST ACTIVEREQUEST 5 DETAIL

         name:                5
         ID:                  5
         ParentID:            5
         dbName:              "test DB"
         InstNum:             5
         ConsumerGrp:         "test group"
         SessID:              5
         SerialNum:           5
         AsmFileNum:          5
         AsmDGNum:            5
         FileIncNum:          5
         ObjNum:              5
         TsNum:               5
         SqlID:               5
         FileType:            "Oracle db data file"
         IoReason:            "test io"
         IoType:              "test read"
         State:               "Queued for Test"
         GdList:              gdName=testGrid,gdOffset=0,gdSize=524288000

8.19.2 LIST ALERTDEFINITION

Purpose

The LIST ALERTDEFINITION command displays all available sources of the alerts on the cell.

Syntax

LIST ALERTDEFINITION [ name |  attribute_filters ]  [attribute_list]  [DETAIL]

Usage Notes

The list of attributes that can be displayed is shown in the following example.

Example 8-116 Listing ALERTDEFINITION Attributes

This example shows the LIST command with the ALERTDEFINITION object.

CellCLI> LIST ALERTDEFINITION StatefulAlert_CG_IO_RQ_LG DETAIL

         name:                   StatefulAlert_CG_IO_RQ_LG
         alertShortName:         CG_IO_RQ_LG
         alertSource:            Metric
         alertType:              Stateful
         description:            "Threshold Alert"
         metricName:             CG_IO_RQ_LG

8.19.3 LIST ALERTHISTORY

Purpose

The LIST ALERTHISTORY command displays all alerts that occurred on the cell.

Syntax

LIST ALERTHISTORY [ name |  attribute_filters ]  [attribute_list]  [DETAIL]

Usage Notes

The list of attributes that can be displayed is shown in Example 8-74.

A WHERE clause can include the ageInMInutes attribute to specify the list is limited to those alerts which have the specified age. For example, the following command would show the alerts created in the previous 15 minutes:

CellCLI> LIST ALERTHISTORY WHERE ageInMinutes < 15

The alerthistory attribute can be used to check for stateful and stateless alerts.

Examples

Example 8-117 shows the LIST command with the ALERTHISTORY object.

Example 8-118 shows open stateful and stateless alerts.

Example 8-119 shows only open stateful alerts. The closed stateful alerts are filtered out.

Example 8-120 shows alerts that have not been cleared.

Example 8-117 Listing ALERTHISTORY Attributes

CellCLI>  LIST ALERTHISTORY 1671443714 DETAIL
          name:                1671443714
          alertSequenceID:     1671443714
          sequenceBeginTime:   1179185707672
          beginTime:           "Sat May 18 10:14:16 PDT 2009"
          endTime:             "Sat May 25 10:14:16 PDT 2009"
          severity:            critical
          alertMessage:        "Errors in file svtrc_2840_10.trc (incident=13):"
          alertShortName:      ADR
          alertNotified:       0
          examinedBy:          johndoe
          alertType:           stateless

CellCLI> LIST ALERTHISTORY WHERE begintime > 'Jun 1, 2009 11:37:00 AM PDT'

         39      2009-10-02T12:26:53-07:00       "ORA-07445: exception
                 encountered: core dump [__kerne l_vsyscall()+5] [6] 
                 [0x408C] [] [] []"
         40      2009-10-06T23:28:06-07:00       "RS-7445 [unknown_function]
                 [signum: 6] [] [] [] [] [ ] []"
         41      2009-10-07T00:50:42-07:00       "RS-7445 [Serv MS not responding]
                 [It will be restart ed] [] [] [] [] [] []"
         42      2009-10-07T02:21:19-07:00       "RS-7445 [unknown_function]
                 [signum: 6] [] [] [] [] [ ] []"

CellCLI> LIST ALERTHISTORY 7 DETAIL
         name:                   7
         alertMessage:           "Flash cache mode is set to WriteBack because
                                 there is dirty data in the flash cache."
         alertSequenceID:        7
         alertShortName:         Software
         alertType:              Stateless
         beginTime:              2012-09-10T13:22:38-07:00
         examinedBy:             
         metricObjectName:       FlashCache
         notificationState:      0
         sequenceBeginTime:      2012-09-10T13:22:38-07:00
         severity:               info
         alertAction:            "If the newly-assigned mode for flash cache is 
                                 not wanted, then change it using the ALTER CELL
                                 command as described in the Oracle Exadata user's
                                 guide."

Example 8-118 Listing Open Stateful and Stateless Alerts

CellCLI> LIST ALERTHISTORY ATTRIBUTES alertsequenceid,name,alerttype    \
         WHERE endtime=null

         1       1       Stateless
         3       3       Stateless
         11      11_1    Stateful

Example 8-119 Listing Open Stateful Alerts

CellCLI> LIST ALERTHISTORY WHERE endtime=null AND alerttype=stateful

Example 8-120 Listing Alerts That Have Not Cleared

CellCLI> LIST ALERTHISTORY WHERE endtime=null

1       2014-11-11T11:08:15-08:00  info      "Factory defaults restored for
 Adapter 0"
3       2014-11-11T11:27:06-08:00  critical   "RS-700 [No IP found in Exadata
 config file] [Check cellinit.ora]
                                               [] [] [] [] [] [] [] [] [] []"
11_1    2014-12-19T12:01:06-08:00  critical    "The HDD disk controller battery
 has failed. All disk drives have been placed in WriteThrough caching mode. Disk
 write performance may be reduced. The flash drives are not affected. Battery
 Serial Number : 1142  Battery Type          : ibbu08  Battery Temperature   : 39
 C  Full Charge Capacity  : 773 mAh  Relative Charge       : 83%  Ambient
 Temperature   : 32 C"

8.19.4 LIST CELL

Purpose

The LIST CELL command displays specified attributes of the cell.

Syntax

LIST CELL [ATTRIBUTES attribute_list] [DETAIL]

Usage Notes

  • The list of attributes that can be displayed is shown in Example 8-75.

  • LIST CELL only lists the local cell. Name and filter options on LIST CELL are not required.

  • To monitor the status of cell components, use the LIST command to verify the value of status, fanStatus, temperatureStatus, and powerStatus.

Examples

Example 8-121 shows the LIST command with the CELL object, and the corresponding output.

Example 8-122 shows how to display cell attributes.

Example 8-123 shows how to display the values of the snmpSubscriber attribute.

Example 8-124 shows how to display the value of the emailFormat attribute.

Example 8-125 shows how to display the value of the locateLEDStatus attribute.

Example 8-126 shows how to display the value of the doNotServiceLEDStatus attribute.

Example 8-127 shows how to display the value of the bbuLearnCycleTime attribute.

Example 8-128 shows how to display the value of the rescuePlan attribute.

Example 8-121 Listing Cell Attributes

CellCLI> LIST CELL ATTRIBUTES name, status, location

         cell01        online        rack5:shelf1

Example 8-122 Verifying the Status of Cell Components

CellCLI> LIST CELL ATTRIBUTES name, status, location, -
         fanStatus, temperatureStatus, powerStatus

         stba2s3         online  dv-2ndFloor     normal  normal  normal

Example 8-123 Displaying the snmpSubscriber Attribute

CellCLI> LIST CELL ATTRIBUTES snmpSubscriber

((host=server1.example.com,port=3873,community=public, type=asr))

Example 8-124 Displaying E-mail Format

CellCLI> LIST CELL ATTRIBUTES emailFormat
         html

Example 8-125 Displaying locateLEDStatus

CellCLI> LIST CELL ATTRIBUTES locateLEDStatus
         off

Example 8-126 Displaying doNotServiceLEDStatus

CellCLI> LIST CELL ATTRIBUTES doNotServiceLEDStatus
         on

Example 8-127 Listing the bbuLearnCycleTime Attribute

CellCLI> LIST CELL ATTRIBUTES bbuLearnCycleTime

Example 8-128 Displaying rescuePlan

CellCLI> LIST CELL ATTRIBUTES rescuePlan

CREATE ROLE "admin"

GRANT PRIVILEGE all actions ON diagpack all attributes WITH all options TO ROLE "admin"

CREATE ROLE "diagRole"

GRANT PRIVILEGE download ON diagpack all attributes WITH all options TO ROLE "diagRole"

GRANT PRIVILEGE create ON diagpack all attributes WITH all options TO ROLE "diagRole"

GRANT PRIVILEGE list ON diagpack all attributes WITH all options TO ROLE "diagRole"

ALTER CELL accessLevelPerm="remoteLoginEnabled", diagHistoryDays="7", metricHistoryDays="7", notificationMethod="mail,snmp", notificationPolicy="warning,critical,clear", snmpSubscriber=((host="localhost", port=162, community="public", type=asr)), bbuLearnCycleTime="2016-10-17T02:00:00-07:00", bbuLearnSchedule="MONTH 1 DATE 17 HOUR 2 MINUTE 0", alertSummaryStartTime="2016-09-21T17:00:00-07:00", alertSummaryInterval=weekly, hardDiskScrubInterval=biweekly, hardDiskScrubFollowupIntervalInDays="14"

ALTER IORMPLAN objective=basic

8.19.5 LIST CELLDISK

Purpose

The LIST CELLDISK command displays attributes for cell disks determined by the specified attributes and filters.

Syntax

LIST CELLDISK [ name |  attribute_filters ]  [attribute_list] [DETAIL]

Usage Notes

The list of attributes that can be displayed is shown in Describing the CELLDISK Object.

Examples

The following example shows the LIST command with the CELLDISK object, and the corresponding output.

Example 8-129 Listing Cell Disk Attributes

CellCLI> LIST CELLDISK CD_01_cell05 ATTRIBUTES size

         136.640625G

CellCLI> LIST CELLDISK WHERE status!=normal ATTRIBUTES name

         CD_01_1_abcd2x3

CellCLI> LIST CELLDISK WHERE DEVICENAME LIKE '/dev/c0d[2-5]' -
         ATTRIBUTES name, size

         CD_01_cell05             139664M

CellCLI> LIST CELLDISK CD_01_cell05 DETAIL

         name:                   CD_01_cell05
         status:                 normal
         comment:                
         id:                     00000117-84d2-ed2c-0000-000000000000
         size:                   139664M
         lun:                    3_1
         freespace:              129424M
         devicepartition:        /dev/c1d0p2
         Devicename:             /dev/c1d0
         diskType:               HardDisk

CellCLI> LIST CELLDISK CD_00_sgsata1 DETAIL

         name:                   CD_00_sgsata1
         comment:                
         creationTime:           2009-07-26T15:31:02-07:00
         deviceName:             /dev/sda
         devicePartition:        /dev/sda3
         diskType:               HardDisk
         errorCount:             0
         freeSpace:              286.96875G
         freeSpaceMap:           offset=102.546875G,size=286.96875G
         id:                     00000122-b930-3e2c-0000-000000000000
         interleaving:           normal_redundancy
         lun:                    0_0
         raidLevel:              0
         size:                   389.515625G
         status:                 normal

8.19.6 LIST DATABASE

Purpose

Displays the specified attributes for active databases.

Syntax

LIST DATABASE [name | attribute_filters] [attribute_list]  [DETAIL]

Usage Notes

The filters option is an expression that determines which active databases should be listed by the command.

The list of attributes that can be displayed is shown in Describing the DATABASE Object.

Examples

The following example shows the LIST command with the DATABASE object, and the corresponding output.

Example 8-130 Listing Database Attributes

CellCLI> LIST DATABASE
         DB01
CellCLI> LIST DATABASE DETAIL
         name:                   DB01
         databaseID:             1234567656
         lastRequestTime:        2016-10-27T07:46:36-07:00
         profile:                GOLD
         flashCacheMin:          4.00390625G
         flashCacheLimit:        4.19921875G
         flashCacheSize:         0

CellCLI> LIST DATABASE DB01
         DB01
CellCLI> LIST DATABASE ATTRIBUTES NAME, PROFILE
         ASM             
         TEST50          GOLD
         TEST100         GOLD
         TEST150         SILVER
         TEST20          GOLD
         TEST200         BRONZE
         TEST180         SILVER
         TEST175         SILVER
         TEST225         BRONZE
         TEST230         BRONZE
         TEST300         
         TEST280         
         TEST245         BRONZE
 
CellCLI> LIST DATABASE ATTRIBUTES NAME, DATABASEID WHERE PROFILE = 'GOLD'
         TEST50          50
         TEST100         100
         TEST20          20

8.19.7 LIST DIAGPACK

Purpose

The LIST DIAGPACK command lists the diagnostic packages in your system, along with their status.

Syntax

LIST DIAGPACK [DETAIL]

Usage Notes

The location of the diagnostic packages is $LOG_HOME.

Examples

Example 8-131 Output of the "list diagpack" Command

This example shows the output of the LIST DIAGPACK command.

CellCLI> LIST DIAGPACK
scab01cel04_diag_2015_09_30T13_29_06_1.tar.bz2  (7 minutes ago)
scab01cel04_2015_09_30T13_13_00_2_1.tar.bz2     (23 minutes ago for alert: 2_1)
scab01cel04_2015_09_30T13_07_10_1_1.tar.bz2     (28 minutes ago for alert: 1_1)

Example 8-132 Output of the "list diagpack" command with the DETAIL option

This example shows the output of the LIST DIAGPACK command with the DETAIL option.

CellCLI> LIST DIAGPACK DETAIL
Name:               scab01cel04_diag_2015_09_30T13_29_06_1.tar.bz2
Time:               Wed, 30 Sep 2015 13:29:06 (7 minutes ago)
Type:               Custom package

Name:               scab01cel04_2015_09_30T13_13_00_2_1.tar.bz2
Time:               Wed, 30 Sep 2015 13:13:00 (23 minutes ago)
Alert ID:           2_1
Alert description:  InfiniBand Port HCA-1:2 indicates invalid state.

Name:               scab01cel04_2015_09_30T13_07_10_1_1.tar.bz2
Time:               Wed, 30 Sep 2015 13:07:10 (28 minutes ago)
Alert ID:           1_1
Alert description:  File system "/" is 84% full

Related Topics

8.19.8 LIST DISKMAP

Purpose

Displays the specified grid disk attributes for a physical disk.

Syntax

LIST DISKMAP

Usage Notes

The list of attributes that can be displayed is shown in Example 8-78.

Examples

The following example shows the LIST command with the DISKMAP object, and the corresponding output.

Example 8-133 Listing Grid Disk Attributes for a Physical Disk

CELLCLI> LIST DISKMAP

Name   PhysicalSerial  SlotNumber    Status  PhysicalSize  CellDisk  DevicePartition  GridDisks
27:0   E0XH34          0             normal   559G         CD_00_sgrcel2   /dev/sda3 "DATA_CD_00_sgrcel2, RECO_CD_00_sgrcel2"

27:1   E0XH2S          1             normal   559G         CD_01_sgrcel2   /dev/sdb3  "DATA_CD_01_sgrcel2, RECO_CD_01_sgrcel2"

27:2   E0Z0CS           2            normal   559G         CD_02_sgrcel2   /dev/sdc   "DATA_CD_02_sgrcel2, DBFS_CD_02_sgrcel2, RECO_CD_02_sgrcel2"
.
.
.

8.19.9 LIST FLASHCACHE

Purpose

The LIST FLASHCACHE command displays attributes for the Exadata Smart Flash Cache determined by the specified attributes.

Syntax

LIST FLASHCACHE [attribute_list] [DETAIL]

Usage Notes

The list of attributes that can be displayed is shown in Example 8-79.

Examples

The following example shows the LIST command with the FLASHCACHE object, and the corresponding output.

Example 8-134 Listing Exadata Smart Flash Cache Attributes

CellCLI> LIST FLASHCACHE

         raw_FLASHCACHE normal

CellCLI> LIST FLASHCACHE DETAIL

         name:                   raw_FLASHCACHE
         cellDisk:               c9FLASH0,FD_FLASH1_raw,FD_FLASH2_raw
         creationTime:           2012-08-04T15:42:42-07:00
         degradedCelldisks:
         effectiveCacheSize:     192M
         id:                     8a0adc84-9088-4c4e-8e1c-b6bcbd5cb1ba
         size:                   192M
         status:                 normal
 

8.19.10 LIST FLASHCACHECONTENT

Purpose

The LIST FLASHCACHECONTENT command displays attributes for the Exadata Smart Flash Cache entries determined by the specified attributes.

Syntax

LIST FLASHCACHECONTENT [attribute_filters] [attribute_list] [DETAIL]

Usage Notes

The list of attributes that can be displayed is shown in Example 8-80.

Examples

Example 8-135 shows the LIST command with the FLASHCACHECONTENT object, and the corresponding output.

Example 8-135 shows a database query for an object in a partitioned table, and then lists the flash cache for the same object. In the example, a partitioned table is created in the database, and then queried for the data object numbers of the partitions. The flash cache on Oracle Exadata Storage Server is then queried.

Example 8-135 Listing Exadata Smart Flash Cache Content Attributes

  CellCLI> LIST FLASHCACHECONTENT DETAIL

           cachedKeepSize:             8192
           cachedSize:                16384
           dbID:                 3557170052
           dbUniqueName:              ACME1
           hitCount:                      4
           hoursToExpiration:            24
           missCount:                      
           objectNumber:                267
           tableSpaceNumber:              1

           cachedKeepSize:                0
           cachedSize:                 8192
           dbID:                 4325252357
           dbUniqueName:              MYODB
           hitCount:                      1
           hoursToExpiration:            23
           missCount:                     1
           objectNumber:              65523
           tableSpaceNumber:              4

Example 8-136 Listing Exadata Smart Flash Cache Content by Database Object

CREATE TABLE parttabl (c1 number) PARTITION BY RANGE(c1) 
(
  PARTITION partt1 VALUES LESS THAN (100), 
  PARTITION partt2 VALUES LESS THAN (200)
);
 
SQL> SELECT SUBSTR(OBJECT_NAME, 0 , 10) OBJ_NAME, SUBOBJECT_NAME, DATA_OBJECT_ID 
     FROM user_objects WHERE OBJECT_NAME LIKE ('PARTT%');
 
OBJ_NAME   SUBOBJECT_NAME                 DATA_OBJECT_ID
---------- ------------------------------ --------------
PARTTABL
PARTTABL   PARTT1                                  63197
PARTTABL   PARTT2                                  63198

CellCLI> LIST FLASHCACHECONTENT WHERE objectNumber=63197 DETAIL
         cachedKeepSize:         0
         cachedSize:             24576
         dbID:                   3722937438
         dbUniqueName:           VIEW6
         hitCount:               0
         missCount:              4
         objectNumber:           63197
         tableSpaceNumber:       0
 
 
  CellCLI> LIST FLASHCACHECONTENT WHERE objectNumber=63198 DETAIL
         cachedKeepSize:         0
         cachedSize:             16384
         dbID:                   3722937438
         dbUniqueName:           VIEW6
         hitCount:               0
         missCount:              2
         objectNumber:           63198
         tableSpaceNumber:       0

8.19.11 LIST FLASHLOG

Purpose

The LIST FLASHLOG command displays attributes for the Oracle Exadata Smart Flash Log entries determined by the specified attributes.

Syntax

LIST FLASHLOG

Usage Notes

The list of attributes that can be displayed is shown in Example 8-81.

Examples

The following example shows the LIST command with the FLASHLOG object, and the corresponding output.

Example 8-137 Listing Oracle Exadata Smart Flash Log Attributes

CellCLI> LIST FLASHLOG

         raw_FLASHLOG normal

CellCLI> LIST FLASHLOG DETAIL

         name:                   raw_FLASHLOG
         id:                     8a0aadc84-908804c4e08e1c-b6bcbd5cb1ba
         creationTime:           2011-01-23T12:34:56-05:00
         status:                 normal
         size:                   512M
         cellDisk:               c9FLASH0,FD_FLASH1_raw,FD_FLASH2_raw
         efficiency:             100

8.19.12 LIST GRIDDISK

Purpose

The LIST GRIDDISK command displays attributes for one or more Oracle Exadata Storage Server grid disks determined by the specified attributes and filters.

Syntax

LIST GRIDDISK [ name |  attribute_filters ]  [attribute_list] [DETAIL]

Usage Notes

The list of attributes that can be displayed is shown in Example 8-82.

The asmDeactivationOutcome attribute can be used to determine if a grid disk can be deactivated without loss of data. This attribute is not included in the list of attributes shown by the DESCRIBE GRIDDISK command. When using this attribute, a YES in the output means the grid disk can be deactivated.

The asmModeStatus attribute can be used to determine the current usage of a grid disk. This attribute is not included in the list of attributes shown by the DESCRIBE GRIDDISK command. The possible values for this attribute are as follows:

  • ONLINE: Oracle ASM is actively using this grid disk.

  • OFFLINE: Oracle ASM has taken this grid disk offline.

  • DROPPED: Oracle ASM has dropped this grid disk.

  • UNUSED: No Oracle ASM instance has used this grid disk on the storage cell.

  • SYNCING: Oracle ASM has started to set this grid disk to online.

  • UNKNOWN: Oracle ASM instances that use the grid disk are not available to query, or Oracle ASM has rejected the query because it is not in a currently-mounted disk group.

When the cachingPolicy attribute is set to none, the associated flash cache is used for write I/O latency capping and logging. It is not used for caching.

Examples

Example 8-138 shows the LIST command with the GRIDDISK object, and the corresponding output.

Example 8-139 shows the asmDeactivationOutcome attribute being used to determine if a grid disk can be deactivated.

Example 8-140 shows the asmModeStatus attribute being used to check the current usage of a grid disk.

Example 8-141 shows the LIST GRIDDISK command being used to check the status of the resize process when the NOWAIT option is used with the ALTER GRIDDISK command.

Example 8-142 shows the LIST GRIDDISK command being used to check the status of grid disks that are being erased.

Example 8-143 shows the LIST GRIDDISK command with the ORDER BY and LIMIT options.

Example 8-138 Listing Grid Disk Attributes

CellCLI> LIST GRIDDISK WHERE cellDisk = 'CD_01_cell05' -
         ATTRIBUTES name, status

         DATA_CD_01_cell05        active
         RECO_CD_01_cell05        active

CellCLI> LIST GRIDDISK DATA_CD_01_cell05 DETAIL

         name:                   DATA_CD_01_cell05
         status:                 active
         comment:                
         id:                     00000117-84d9-0096-0000-000000000000
         creationTime:           2009-01-16T17:04:49-06:00
         cellDisk:               CD_01_cell05
         offset:                 0
         availableTo:            
         size:                   10G
         errorCount:             0
         diskType:               HardDisk
         cachedBy:               FD_01_FLASH, FD02_FLASH, FD03_FLASH
         cachingPolicy:          default

CellCLI> LIST GRIDDISK DATA_CD_01_cell05 ATTRIBUTES size

         136.640625G

CellCLI> LIST GRIDDISK WHERE status!=active ATTRIBUTES name

         data_CD_01_1_abcd2x3

CellCLI> LIST GRIDDISK data4_CD_09_sgsata1 DETAIL

         name:                   data4_CD_09_sgsata1
         availableTo:            
         cellDisk:               CD_09_sgsata1
         comment:                
         creationTime:           2009-07-26T17:09:46-07:00
         diskType:               HardDisk
         errorCount:             0
         id:                     00000122-b98a-a47a-0000-000000000000
         offset:                 27.546875G
         size:                   75G
         status:                 active

Example 8-139 Determining if a Grid Disk can be Deactivated

CellCLI> LIST GRIDDISK ATTRIBUTES name, asmDeactivationOutcome

         QUAL_CD_00_sgsas1       Yes
         PROD_CD_02_sgsas1       Cannot de-activate due to other offline disks in 
                                 the diskgroup
         TEST_CD_03_sgsas1       Yes
         DATA_CD_04_sgsas1       Yes
         DATA_CD_05_sgsas1       Yes
         DATA_CD_06_sgsas1       Yes
         RECO_CD_01_sgsas1       Cannot de-activate due to other offline disks in 
                                 the diskgroup
         DATA_CD_08_sgsas1       Yes
         DATA_CD_09_sgsas1       Yes
         DATA_CD_10_sgsas1       Yes
         DATA_CD_11_sgsas1       Yes

Example 8-140 Viewing the Current Usage of a Grid Disk

CellCLI> LIST GRIDDISK ATTRIBUTES name, asmModeStatus

         QUAL_CD_00_sgsas1        UNUSED
         RECO_CD_01_sgsas1        OFFLINE
         PROD_CD_02_sgsas1        SYNCING
         TEST_CD_03_sgsas1        UNKNOWN
         DATA_CD_04_sgsas1        ONLINE
         DATA_CD_05_sgsas1        ONLINE
         DATA_CD_06_sgsas1        ONLINE
         DATA_CD_07_sgsas1        ONLINE
         DATA_CD_08_sgsas1        ONLINE
         DATA_CD_09_sgsas1        ONLINE
         DATA_CD_10_sgsas1        ONLINE
         DATA_CD_11_sgsas1        ONLINE

Example 8-141 Checking the Status Using the LIST GRIDDISK Command

CellCLI> LIST GRIDDISK DETAIL

         name:                   gd0
         availableTo:
         cellDisk:               c9standby0
         comment:
         creationTime:           2009-07-09T09:07:36-07:00
         diskType:               HardDisk
         errorCount:             0
         id:                     00000122-6045-173b-0000-000000000000
         resizeStatus:           Resize in progress
         offset:                 48M
         size:                   48M
         status:                 active

Example 8-142 Checking the Status of Secure Erase

CellCLI> LIST GRIDDISK
         DATA_CD_00_sgsas1     active
         DATA_CD_05_sgsas1     active
         DATA_CD_06_sgsas1     erase in progress
         DATA_CD_07_sgsas1     erase in progress

Example 8-143 Listing Grid Disk Attributes Using ORDER BY and LIMIT

CellCLI> LIST GRIDDISK attributes name, size ORDER BY size,name desc LIMIT 6
         standby0        208M
         controlfile0    304M
         logfile1        800M
         logfile0        800M
         datafile4       1.453125G
         datafile3       1.453125G

8.19.13 LIST IBPORT

Purpose

The LIST IBPORT command displays attributes for InfiniBand ports determined by the specified attributes and filters.

Syntax

LIST IBPORT  [ name |  attribute_filters ]  [attribute_list] [DETAIL]

Usage Notes

The list of attributes that can be displayed is shown in Example 8-83.

If the activeSlave attributes for both InfiniBand ports on a server are not listed, then active-active bonding is being used. If an activeSlave attribute is TRUE, then active-passive bonding is being used.

Examples

The following example shows the LIST command with the IBPORT object, and the corresponding output.

Example 8-144 Listing IBPORT Attributes

CellCLI> LIST IBPORT
         HCA-1:1         Active
         HCA-1:2         Active

CellCLI> LIST IBPORT DETAIL
         name:                   HCA-1:1
         activeSlave:            TRUE
         dataRate:               "40 Gbps"
         hcaFWVersion:           2.7.0
         id:                     0x00212800013e8c67
         lid:                    20
         linkDowned:             0
         linkIntegrityErrs:      0
         linkRecovers:           0
         physLinkState:          LinkUp
         portNumber:             1
         rcvConstraintErrs:      0
         rcvData:                84653709
         rcvErrs:                0
         rcvRemotePhysErrs:      0
         status:                 Active
         symbolErrs:             0
         vl15Dropped:            0
         xmtConstraintErrs:      0
         xmtData:                84572496
         xmtDiscards:            0

         name:                   HCA-1:2
         activeSlave:            FALSE
         dataRate:               "40 Gbps"
         hcaFWVersion:           2.7.0
         id:                     0x00212800013e8c68
         lid:                    21
         linkDowned:             0
         linkIntegrityErrs:      0
         linkRecovers:           0
         physLinkState:          LinkUp
         portNumber:             2
         rcvConstraintErrs:      0
         rcvData:                79355427
         rcvErrs:                0
         rcvRemotePhysErrs:      0
         status:                 Active
         symbolErrs:             0
         vl15Dropped:            0
         xmtConstraintErrs:      0
         xmtData:                79274016
         xmtDiscards:            0

8.19.14 LIST IORMPLAN

Purpose

The LIST IORMPLAN command lists the current plan of the local cell.

Syntax

LIST IORMPLAN [attribute_list]  [DETAIL]

Usage Notes

The list of attributes that can be displayed is shown in Example 8-84.

Examples

The following example shows the LIST command with the IORMPLAN object, and the corresponding output.

Example 8-145 Listing IORMPLAN Attributes

CellCLI> LIST IORMPLAN ATTRIBUTES status

         active

CellCLI> LIST IORMPLAN DETAIL

         name:                cell01_IORMPLAN
         catPlan:             name=administrative,level=1,allocation=80
                              name=interactive,level=2,allocation=90
                              name=batch,level=3,allocation=80
                              name=maintenance,level=4,allocation=50
                              name=other,level=4,allocation=50
         dbPlan:              name=sales_prod,level=1,allocation=80
                              name=finance_prod,level=1,allocation=20
                              name=sales_dev,level=2,allocation=100
                              name=sales_test,level=3,allocation=50
                              name=other,level=3,allocation=50
         objective:           balanced
         status:              active

8.19.15 LIST IORMPROFILE

Purpose

The LIST IORMPROFILE command enables you to list IORM profiles. To see which databases are associated with an IORM profile, use the LIST DATABASE command with the new PROFILE attribute.

Syntax

LIST IORMPROFILE [name | filters]

Usage Notes

name specifies the IORM profile to display.

filters specifies an expression that determines which IORM profiles to display.

If name and filters are omitted, all the IORM profiles are displayed.

Examples

The following example shows the LIST IORMPROFILE command, and the corresponding output.

Example 8-146 LIST IORMPROFILE

CellCLI> LIST IORMPROFILE
GOLD
SILVER
BRONZE

8.19.16 LIST KEY

Purpose

The LIST KEY command displays key values for clients determined by the specified attributes and filters.

Syntax

LIST KEY [name | filters] [attribute_list] [DETAIL]

LIST KEY [FOR {ASMCLUSTER | CELL | LOCAL CELL | REMOTE CELL}] [DETAIL]

Usage Notes

  • The key value assigned to a client must match the keys in the cellkey.ora files on cells, and the Oracle ASM and database host computers.

  • The output of the command might show a “type” attribute, which is new to Oracle Exadata 12.2.1.1.0. Values for this attribute include ASMCLUSTER, LOCAL-CELL, REMOTE-CELL, and CELL. See the examples below.

  • The FOR [LOCAL | REMOTE] CELL and FOR ASMCLUSTER clauses are also new to Oracle Exadata 12.2.1.1.0. They indicate that the command is to display only the keys with the specified type.

  • name specifies the key to display.

Examples

The following example shows the LIST command with the KEY object, and the corresponding output.

Example 8-147 Listing KEY Attributes

CellCLI>  LIST KEY db1 DETAIL
         name:                   db1
         key:                    b67d5587fe728118af47c57ab8da650a


CellCLI>  LIST KEY
         db1     b67d5587fe728118af47c57ab8da650a
         db456   118af47c57ab8da650ab67d5587fe728


CellCLI>  LIST KEY asm1 DETAIL
         name:         asm1
         key:          b67d5587fe728118af47c57ab8da650a
         type:         ASMCLUSTER


CellCLI>  LIST KEY
         db1     b67d5587fe728118af47c57ab8da650a
         asm1    118af47c57ab8da650ab67d5587fe728   ASMCLUSTER


CellCLI>  LIST KEY FOR CELL DETAIL
         key: fa292e11b31b210c4b7a24c5f1bb4d32
         type: CELL

8.19.17 LIST LUN

Purpose

The LIST LUN command displays attributes for LUNs determined by the specified attributes and filters.

Syntax

LIST LUN [ name |  attribute_filters ]  [attribute_list] [DETAIL]

Usage Notes

The list of attributes that can be displayed is shown in Example 8-86.

Examples

The following example shows the LIST command with the LUN object, and the corresponding output.

Example 8-148 Listing LUN Attributes

CellCLI> LIST LUN
         0_0     0_0     normal
         0_1     0_1     normal
         0_2     0_2     normal
         0_3     0_3     normal
         0_4     0_4     normal
         0_5     0_5     normal
         0_6     0_6     normal
         0_7     0_7     normal
         0_8     0_8     normal
         0_9     0_9     normal
         0_10    0_10    normal
         0_11    0_11    normal
         1_0     1_0     normal
         1_1     1_1     normal
         1_2     1_2     normal
         1_3     1_3     normal
         2_0     2_0     normal
         2_1     2_1     normal
         2_2     2_2     normal
         2_3     2_3     normal
         4_0     4_0     normal
         4_1     4_1     normal
         4_2     4_2     normal
         4_3     4_3     normal
         5_0     5_0     normal
         5_1     5_1     normal
         5_2     5_2     normal
         5_3     5_3     normal
 
CellCLI> LIST LUN 0_0 DETAIL
         name:                   0_0
         cellDisk:               CD_00_sgsas1
         deviceName:             /dev/sda
         diskType:               HardDisk
         id:                     0_0
         isSystemLun:            TRUE
         lunAutoCreate:          TRUE
         lunSize:                558.40625G
         lunUID:                 0_0
         physicalDrives:         20:0
         raidLevel:              0
         status:                 normal

CellCLI> LIST LUN 1_0 DETAIL
         name:                   1_0
         cellDisk:               FD_00_sgsas1
         deviceName:             /dev/sdr
         diskType:               FlashDisk
         id:                     1_0
         isSystemLun:            FALSE
         lunAutoCreate:          FALSE
         lunSize:                22.8880615234375G
         overProvisioning:       100.0
         physicalDrives:         [9:0:0:0]
         status:                 normal

8.19.18 LIST METRICCURRENT

Purpose

The LIST METRICCURRENT command displays a list of collections of all metrics.

Syntax

LIST METRICCURRENT [ name |  attribute_filters ]  [attribute_list]  [DETAIL]

Usage Notes

  • The list of attributes that can be displayed is shown in Example 8-87.

  • To reduce the size of the output when you run the LIST METRICCURRENT command, use filters.

Examples

Example 8-149 shows the LIST command with filters to display information about the METRICCURRRENT object, and the corresponding output.

Example 8-150 shows the LIST METRICCURRENT command with the ORDER BY and LIMIT options.

Example 8-149 Listing METRICCURRENT Attributes

CellCLI> LIST METRICCURRENT WHERE objectType = 'CELLDISK'

         CD_IO_TM_W_SM_RQ        c9controlfile0  205.5 us/request
         CD_IO_TM_W_SM_RQ        c9datafile0     93.3 us/request
         CD_IO_TM_W_SM_RQ        c9datafile1     0.0 us/request
         CD_IO_TM_W_SM_RQ        c9datafile2     110.5 us/request
         CD_IO_TM_W_SM_RQ        c9datafile3     0.0 us/request
         CD_IO_TM_W_SM_RQ        c9datafile4     541.5 us/request
         CD_IO_TM_W_SM_RQ        c9logfile0      181.2 us/request
         CD_IO_TM_W_SM_RQ        c9logfile1      0.0 us/request
         CD_IO_TM_W_SM_RQ        c9standby0      130.4 us/request

CellCLI> LIST METRICCURRENT WHERE name = CD_IO_TM_W_SM_RQ   -
         AND metricObjectName = c9datafile4 DETAIL   

         name:                   CD_IO_TM_W_SM_RQ
         alertState:             normal
         collectionTime:         2009-07-01T15:19:25-07:00
         metricObjectName:       c9datafile4
         metricType:             Rate
         metricValue:            0.0 us/request
         objectType:             CELLDISK

CellCLI> LIST METRICCURRENT CG_IO_UTIL_LG 
         CG_IO_UTIL_LG   RDB1.BATCH_GROUP                                0 % 
         CG_IO_UTIL_LG   RDB1.INTERACTIVE_GROUP                          0 % 
         CG_IO_UTIL_LG   RDB1.OTHER_GROUPS                               0 % 
         CG_IO_UTIL_LG   RDB2.BATCH_GROUP                               0 % 
         CG_IO_UTIL_LG   RDB2.INTERACTIVE_GROUP                         0 % 
         CG_IO_UTIL_LG   RDB2.OTHER_GROUPS                              0 % 

Example 8-150 Listing METRICCURRENT Attributes Using ORDER BY and LIMIT

CellCLI> LIST METRICCURRENT attributes name, metricObjectName, alertState,   \
         metricValue ORDER BY metricValue desc, metricObjectName asc,        \
         name desc LIMIT 3

CD_IO_TM_R_LG   c9FLASH0   normal    160,514,088   us
CD_IO_TM_R_LG   c9FLASH1   normal    156,659,463   us
DB_IO_TM_SM     ASM        normal    33,111,890    us

8.19.19 LIST METRICDEFINITION

Purpose

The LIST METRICDEFINITION command displays a list of metric definitions on the cell.

Syntax

LIST METRICDEFINITION [ name |  attribute_filters ]  [attribute_list]  [DETAIL]

Usage Notes

The list of attributes that can be displayed is shown in Example 8-88.

Examples

The following example shows the LIST command with the METRICDEFINITION object, and the corresponding output.

Example 8-151 Listing METRICDEFINITION Attributes

CellCLI> LIST METRICDEFINITION WHERE objectType ='CELL' DETAIL

         name:                   CL_CPUT
         description:            "Cell CPU Utilization is the percentage of time
                                 over the previous minute that the system
                                 CPUs were not idle (from /proc/stat)."
         metricType:             Instantaneous
         objectType:             CELL
         unit:                   %
...

8.19.20 LIST METRICHISTORY

Purpose

The LIST METRICHISTORY command displays a list of individual metrics.

Syntax

LIST METRICHISTORY [ name | attribute_filters ]  [attribute_list]  
                   {over_specification] [MEMORY] [DETAIL]

Usage Notes

  • The list of attributes that can be displayed is shown in Example 8-89.

  • The retention period for metric history entry files is specified by the metricHistoryDays cell attribute. You can modify this setting with the CellCLI ALTER CELL command.

  • The over_specification syntax is as follows:

    OVER number [aggregation_type [aggregation_type]...] 
    

    In the preceding syntax, number is amount of time in minutes for the aggregation, and aggregation_type can be max, min, or avg.

  • A WHERE clause can include the ageInMinutes attribute to specify the list is limited to those metrics which have the specified age. For example, the following command would show the metrics created in the previous 15 minutes:

    CellCLI> LIST METRICHISTORY WHERE ageInMinutes < 15
    

Examples

Example 8-152 shows the LIST command with the METRICHISTORY object, and the corresponding output. To reduce the size of the output when you run the LIST METRICHISTORY command, use filters.

Example 8-153 shows the LIST METRICHISTORY command with the over and memory attributes.

Example 8-154 shows the LIST METRICHISTORY command with the ORDER BY and LIMIT options.

Example 8-152 Listing METRICHISTORY Attributes

CellCLI> LIST METRICHISTORY WHERE name like 'CL_.*'           -
            AND collectionTime > '2009-07-01T15:28:36-07:00'

         CL_RUNQ         stbcr03_2       6.0     2009-07-01T15:28:37-07:00
         CL_CPUT         stbcr03_2       47.6 %  2009-07-01T15:29:36-07:00
         CL_FANS         stbcr03_2       1       2009-07-01T15:29:36-07:00
         CL_TEMP         stbcr03_2       0.0 C   2009-07-01T15:29:36-07:00
         CL_RUNQ         stbcr03_2       5.2     2009-07-01T15:29:37-07:00

The following example shows the LIST METRICHISTORY command with the over and memory attributes.

Example 8-153 Listing METRICHISTORY Using the OVER and MEMORY Attributes

CellCLI> LIST METRICHISTORY cl_cput OVER 10 MIN MAX MEMORY
        CL_CPUT         firstcell       55.0 %  2009-11-15T06:00:17-08:00      55.0 %   57.1 %
        CL_CPUT         firstcell       54.7 %  2009-11-15T06:10:17-08:00      54.7 %   56.3 %
        CL_CPUT         firstcell       54.8 %  2009-11-15T06:20:18-08:00      54.7 %   57.2 %
        CL_CPUT         firstcell       55.0 %  2009-11-15T06:30:18-08:00      54.3 %   55.9 %
        CL_CPUT         firstcell       55.0 %  2009-11-15T06:40:18-08:00      54.9 %   57.0 %
        CL_CPUT         firstcell       55.1 %  2009-11-15T06:50:18-08:00      54.8 %   56.4 %
        CL_CPUT         firstcell       58.0 %  2009-11-15T07:00:18-08:00      55.2 %   58.0 %
        CL_CPUT         firstcell       55.5 %  2009-11-15T07:10:18-08:00      55.5 %   67.5 % 

The following example shows the LIST METRICHISTORY command with the ORDER BY and LIMIT options.

Example 8-154 Listing METRICHISTORY Attributes Using ORDER BY and LIMIT

CellCLI> LIST METRICHISTORY WHERE name like '.*IO_RQ.*' DETAIL ORDER BY   \
         metricValue desc, metricObjectName desc LIMIT 4

name:                   CT_FD_IO_RQ_SM
alertState:             normal
collectionTime:         2014-05-23T10:59:06-07:00
metricObjectName:       OTHER
metricType:             Cumulative
metricValue:            3,211,568 IO requests
objectType:             IORM_CATEGORY
 
name:                   CT_FD_IO_RQ_SM
alertState:             normal
collectionTime:         2014-05-23T10:58:06-07:00
metricObjectName:       OTHER
metricType:             Cumulative
metricValue:            3,211,568 IO requests
objectType:             IORM_CATEGORY
 
name:                   CT_FD_IO_RQ_SM
alertState:             normal
collectionTime:         2014-05-22T17:23:45-07:00
metricObjectName:       OTHER
metricType:             Cumulative
metricValue:            3,211,568 IO requests
objectType:             IORM_CATEGORY
 
name:                   CT_FD_IO_RQ_SM
alertState:             normal
collectionTime:         2014-05-22T17:21:41-07:00
metricObjectName:       OTHER
metricType:             Cumulative
metricValue:            3,211,568 IO requests
objectType:             IORM_CATEGORY

8.19.21 LIST OFFLOADGROUP

Purpose

The LIST OFFLOADGROUP command displays the attributes for offload groups.

Syntax

LIST OFFLOADGROUP [name | filters] [attribute_list] [DETAIL]

Usage Notes

  • The name and filters parameters specify the offload groups for which you want to display the attributes.

    • name specifies the name of an offload group.

    • filters specifies an expression to match one or more offload groups.

    • If neither name nor filters is specified, the command lists the attributes for all offload groups.

  • The attribute_list parameter specifies one or more attributes for which you want to view. The attribute_list begins with the ATTRIBUTES keyword. If specifying more than one attribute, separate the attributes with a comma:

    ATTRIBUTES { attr1 [, attr2]... }
    

    If the attribute_list parameter is omitted, the command displays all attributes.

  • If the DETAIL parameter is used, the command displays an attribute descriptor for each attribute.

Examples

Example 8-155 Displaying All Offload Groups in Detail

The following command lists all the attributes for all offload groups.

LIST OFFLOADGROUP DETAIL

Example 8-156 Displaying the Attributes for an Offload Group

The following command lists all the attributes for an offload group named "offloadgroup1".

LIST OFFLOADGROUP offloadgroup1

Example 8-157 Displaying Specific Attributes

The following command lists the name and package attributes for all offload groups.

LIST OFFLOADGROUP ATTRIBUTES name, package

Related Topics

8.19.22 LIST PHYSICALDISK

Purpose

The LIST PHYSICALDISK command displays attributes for one or more physical disks determined by the specified attributes and filters.

Syntax

LIST PHYSICALDISK [ name |  attribute_filters ]  [attribute_list]  [DETAIL]

Usage Notes

The list of attributes that can be displayed is shown in Example 8-90.

When a physical disk is performing a power cycle, the status of the disk is included in the output. The status options are Normal-DiskPoweredOn, Normal-DiskPoweredOff, ProactiveFailure-DiskPoweredOn, and ProactiveFailure-DiskPoweredDown. If physical disk status shows as failed, perform a power cycle on the disk to verify the status of the physical disk.

Example 8-158 Listing Physical Disk Attributes

This example shows the LIST command with the PHYSICALDISK object, and the corresponding output.

CellCLI> LIST PHYSICALDISK
         20:0            K68DWJ          normal
         20:1            K7YXUJ          normal
         20:2            K7TYEJ          normal
         20:3            K7BJMJ          normal
         20:4            K5B4SM          normal
         20:5            KEBTDJ          normal
         20:6            K4URJJ          normal
         20:7            K5E1DM          normal
         20:8            K7VL6J          normal
         20:9            K7N5NJ          normal
         20:10           K7Z3KJ          normal
         20:11           K504ZM          normal
         FLASH_1_0       1030M03RK1      normal
         FLASH_1_1       1030M03RJN      normal
         FLASH_1_2       1030M03RJH      normal
         FLASH_1_3       1030M03RJD      normal
         FLASH_2_0       1027M03N6X      normal
         FLASH_2_1       1027M03NMN      normal
         FLASH_2_2       1027M03N6Y      normal
         FLASH_2_3       1027M03N6W      normal
         FLASH_4_0       1025M03EJ3      normal
         FLASH_4_1       1025M03EJ2      normal
         FLASH_4_2       1025M03EHU      normal
         FLASH_4_3       1025M03EKE      normal
         FLASH_5_0       1028M03QP8      normal
         FLASH_5_1       1028M03QNA      normal
         FLASH_5_2       1028M03QKU      normal
         FLASH_5_3       1028M03QHN      normal

CellCLI> LIST PHYSICALDISK 20:0 DETAIL
         name:                   20:0
         deviceId:               46
         deviceName:             /dev/sda
         diskType:               HardDisk
         enclosureDeviceId:      20
         errOtherCount:          0
         luns:                   0_0
         makeModel:              "HITACHI HUS1560SCSUN600G"
         physicalFirmware:       A8C0
         physicalInsertTime:     2017-07-27T07:03:00-04:00
         physicalInterface:      sas
         physicalSerial:         K68DWJ
         physicalSize:           558.9120712280273G
         slotNumber:             0
         status:                 normal

CellCLI> LIST PHYSICALDISK FLASH_5_3 DETAIL
         name:                   FLASH_5_3
         deviceName:             /dev/sdx
         diskType:               FlashDisk
         luns:                   5_3
         makeModel:              "Sun Flash Accelerator F20 PCIe Card"
         physicalFirmware:       D21Y
         physicalInsertTime:     2017-07-27T07:03:01-04:00
         physicalSerial:         1028M03QHN
         physicalSize:           22.8880615234375G
         slotNumber:             "PCI Slot: 5; FDOM: 3"
         status:                 normal

8.19.23 LIST PLUGGABLEDATABASE

Purpose

Displays the specified attributes for active pluggable databases.

Syntax

LIST PLUGGABLEDATABASE [name | attribute_filters] [attribute_list]  [DETAIL]

Usage Notes

The filters option is an expression that determines which active pluggable databases should be listed by the command.

Examples

The following example shows the LIST PLUGGABLEDATABASE command and the corresponding output.

Example 8-159 Listing Pluggable Database Attributes

CellCLI> LIST PLUGGABLEDATABASE
         PDB$SEED
         CDB1_PDB1
         NEWPDB1
         NEWPDB2

CellCLI> LIST PLUGGABLEDATABASE DETAIL
         name:                   PDB$SEED
         pdbID:                  385656752
         containerName:          CDB1
         flashCacheMin:          0
         flashCacheLimit:        0
         flashCacheSize:         0 

         name:                   CDB1_PDB1
         pdbID:                  2850864136
         containerName:          CDB1
         flashCacheMin:          200G
         flashCacheLimit:        315G
         flashCacheSize:         0

         name:                   NEWPDB1
         pdbID:                  1674914558
         containerName:          CDB1
         flashCacheMin:          20G
         flashCacheLimit:        157G
         flashCacheSize:         0

         name:                   NEWPDB2
         pdbID:                  2392787216
         containerName:          CDB1
         flashCacheMin:          20G
         flashCacheLimit:        157G
         flashCacheSize:         0

8.19.24 LIST QUARANTINE

Purpose

The LIST QUARANTINE command displays specified attributes for quarantines.

Syntax

LIST QUARANTINE [ name |  attribute_filters ]  [attribute_list] [DETAIL]

Examples

The following example shows the LIST command with the QUARANTINE object.

Example 8-160 Listing QUARANTINE Attributes

CellCLI> LIST QUARANTINE  DETAIL

CellCLI> LIST QUARANTINE where comment like 'added.*'

Related Topics

8.19.25 LIST ROLE

Purpose

The LIST ROLE command displays the specified attributes for a role.

Syntax

LIST ROLE [name | filters] [attribute_list] [DETAIL] 

Usage Notes

  • name is the name of the role.

  • filters is an expression that determines which roles are displayed.

  • attribute_list is the attributes to display. The ALL option can be used to display all attributes.

  • The DETAIL option formats the output as an attribute on each line, with an attribute descriptor preceding each value.

Examples

The following example shows the LIST ROLE command.

Example 8-161 Displaying a Role

CellCLI> LIST ROLE DETAIL

CellCLI> LIST ROLE where name like 'gd_*'

8.19.26 LIST SOFTWAREHISTORY

Purpose

The LIST SOFTWAREHISTORY command displays a list of final states for past software updates.

Syntax

LIST SOFTWAREHISTORY [attribute_filters] [attribute_list] [DETAIL] 

Example 8-162 Displaying the History of a Scheduled Software Update

By default, only the update name and status are shown.

CellCLI> LIST SOFTWAREHISTORY
  12.2.1.2.0.170509  Last update completed at: 2017-05-20T08:00:57-07:00
  12.2.1.2.0.170520  Last update completed at: 2017-05-21T06:39:54-07:00
  12.2.1.2.0.17052   Last update completed at: 2017-06-08T08:56:45-07:00
  12.2.1.2.0.170603  Last update completed at: 2017-06-08T16:03:17-07:00

Example 8-163 Displaying the Detailed History of a Specific Software Update

This example shows the detailed software update history for a particular update which is referenced by its name.

CellCLI> LIST SOFTWAREHISTORY WHERE name='12.2.1.2.0.170808.1' DETAIL
         name:                   12.2.1.2.0.170808.1
         status:                 Upgrade failed. See alerts at: 2017-08-10T10:56:15-07:00

8.19.27 LIST SOFTWAREUPDATE

Purpose

The LIST SOFTWAREUPDATE command displays the status of the most recently scheduled update.

Syntax

LIST SOFTWAREUPDATE [attribute_list] [DETAIL] 

Usage Notes

The possible states for the software update are:

  • Ready to update at: update_time

  • Downloading

  • Checking prerequisites

  • Prerequisites failed. See alerts.

  • Last update completed at: update_time

  • Running

  • Upgrade failed. See alerts.

Example 8-164 Displaying the Status of a Scheduled Software Update

By default, only the update name and status are shown.

CellCLI> LIST SOFTWAREUPDATE
  12.2.1.2.0.170603   Last update completed at: 2017-06-08 16:03:17 -0700

Example 8-165 Displaying the Detailed Status of a Scheduled Software Update

By default, only the update name and status are shown.

CellCLI> LIST SOFTWAREUPDATE DETAIL
         name:                   12.2.1.2.0.170808.1
         status:                 Upgrade failed. See alerts
         store:                  https://mystore_url:4443
         time:                   2017-08-10T10:35:00-07:00

8.19.28 LIST THRESHOLD

Purpose

The LIST THRESHOLD command displays attributes for one or more thresholds determined by the specified attributes and filters.

Syntax

LIST THRESHOLD [ name |  attribute_filters ]  [attribute_list] [DETAIL]

Usage Notes

The list of attributes that can be displayed is shown in Example 8-94.

Examples

The following example shows the LIST command with the THRESHOLD object, and the corresponding output.

Example 8-166 Listing Threshold Attributes

CellCLI> LIST THRESHOLD

         ct_io_wt_rq.interactive
         db_io_rq_sm_sec.db123
         ....

CellCLI> LIST THRESHOLD ct_io_wt_rq.interactive DETAIL

         comparison:             =
         critical:               20.0
         name:                   ct_io_wt_rq.interactive
         observation:            5
         occurences:             2
         warning:                10.0

CellCLI> LIST THRESHOLD db_io_rq_sm_sec.db123 DETAIL  

         comparison:             >
         name:                   db_io_rq_sm_sec.db123
         critical:               120.0

8.19.29 LIST USER

Purpose

The LIST USER command displays the specified attributes for a user.

Syntax

LIST USER [name | filters] [attribute_list] [DETAIL] 

Usage Notes

  • name is the user name.

  • filters is an expression that determines which users are displayed.

  • attribute_list is the attributes to display. The ALL option can be used to display all attributes.

  • The DETAIL option formats the output as an attribute on each line, with an attribute descriptor preceding each value.

Examples

The following example shows the LIST USER command.

Example 8-167 Using the LIST USER Command

CellCLI> LIST USER DETAIL

CellCLI> LIST USER where name like 'agarcia' DETAIL
         name:                   agarcia
         roles:                  role=gd_monitor
         Privileges:             object=griddisk 
                                 verb=list
                                 attributes=all attributes
                                 options= all options

8.20 QUIT

Purpose

The QUIT command exits from the CellCLI utility, and returns control to the operating system prompt.

Syntax

QUIT

QUIT has the same functionality as the EXIT command.

8.21 REVOKE

Purpose

The REVOKE command removes privileges and roles.

Syntax

REVOKE object_type [name] FROM sub_object_type [sub_object_name]

Usage Notes

  • object_type can be as follows:

    • PRIVILEGE

    • ROLE

  • The following can be used for PRIVILEGE object type:

    • name is in the following format:

      { ALL ACTIONS | action } ON { ALL OBJECTS | object }  { ALL ATTRIBUTES | \
      ATTRIBUTES attribute1 [, attribute2, ...] }  { WITH ALL OPTIONS |        \
      WITH OPTIONS option1 [, option2, ...] }
      
    • The sub_object_type must be ROLE.

    • The sub_object_name is the name of the role.

  • The following can be used for the ROLE object type:

    • name is the role name.

    • The sub_object_type must be USER.

    • The sub_object_name is the name of the user.

Related Topics

8.21.1 REVOKE PRIVILEGE

Purpose

The REVOKE PRIVILEGE command revokes privileges from a role.

Syntax

REVOKE PRIVILEGE { ALL ACTIONS | action } ON { ALL OBJECTS | object } { ALL ATTRIBUTES | ATTRIBUTES attribute1 [, attribute2...] } { WITH ALL OPTIONS | WITH OPTIONS option1 [, option2, ...] } FROM ROLE { ALL | role1 [, role2, ...] }

Usage Notes

  • action is the command.

  • object is object type for the action.

  • attribute are the attributes for the object.

  • option are the options for the object.

  • role is the name of the role from which to revoke privileges.

  • The ALL ACTIONS argument revokes privileges for all actions.

  • The ALL OBJECTS argument revokes privileges for all objects.

  • The ALL ATTRIBUTES argument revokes privileges for all attributes.

  • The WITH ALL OPTIONS argument revokes privileges for all options.

Examples

The following example shows the REVOKE PRIVILEGE command.

Example 8-168 Revoking a Privilege

CellCLI> REVOKE PRIVILEGE ALL ACTIONS ON ALL OBJECTS ALL ATTRIBUTES -
         WITH ALL OPTIONS FROM ROLE ALL

CellCLI> REVOKE PRIVILEGE list on griddisk ATTRIBUTES name,size     -
         WITH OPTIONS detail FROM ROLE gd_monitor

8.21.2 REVOKE ROLE

Purpose

The REVOKE ROLE command revokes the role for a user.

Syntax

REVOKE ROLE { ALL | role1 [, role2, ...] } FROM USER { ALL | user1 [, user2...] }

Usage Notes

  • role is the name of a role.

  • user is the name of a user.

  • The ALL argument revokes all roles from the user.

  • The FROM USER ALL argument revokes the role from all users.

Examples

The following example shows how to revoke a role from a user.

Example 8-169 Revoking a Role From a User

CellCLI> REVOKE ROLE gd_monitor FROM USER jdoe 

8.22 SET

Purpose

The SET command sets parameter options in the CellCLI environment.

Syntax

SET DATEFORMAT {LOCAL | STANDARD}
SET ECHO [ON | OFF]

The SET DATEFORMAT command controls the format of displayed dates. For commands that accept dates, the standard date-time format is recommended. The local format is also accepted. The standard format is recommended for scripts because that format is less sensitive to the time zone, region, and locale changes that might occur when running a script.

The SET ECHO command controls whether to echo commands in a script that is run with @ or START. The ON option displays the commands on screen. The OFF option suppresses the display. The SET ECHO command does not affect the display of commands entered interactively or redirected from the operating system.

Example 8-170 Setting the Date Format with the SET Command

This example shows an example of the SET command.

SET DATEFORMAT STANDARD

8.23 SPOOL

Purpose

The SPOOL command writes (spools) the results of commands to the specified file on the cell file system.

Syntax

SPO[OL] [file_name [ CRE[ATE] | REP[LACE] | APP[END] ] | OFF]

If you issue SPOOL file_name with no option, then the output is spooled to that file whether or not the file already exists. The REPLACE option is the default behavior.

The SPOOL options are described in the following table.

Table 8-22 SPOOL Options

Option Description

APPEND

Adds the results to the end of the file specified.

CREATE

Creates a new file with the name specified, and raises an error if the file exists.

file_name

Names the file to which the results are written. It can be specified with a fully-qualified path name, or with a partially-qualified path name relative to the current directory.

no option

Displays the name of the current spool target file, if any.

OFF

Stops writing (spooling) output to the file.

REPLACE

Replaces the contents of an existing specified file. If the file does not exist, then REPLACE creates the file. This is the default behavior.

8.24 START and @

Purpose

The START or @ command runs the CellCLI commands in the specified script file.

Syntax

STA[RT] file_name
@file_name

The START and @ both require the option file_name. It is the name of the script file that contains the CellCLI commands. If the file name does not include a fully-qualified path, then the CellCLI utility searches for the file relative to the current directory.

The START or @ command is useful when entering long or multiple CellCLI commands. For example, all the commands in Example 8-5 or Example 8-6 can be entered in a text file named alter_cell, then run with START alter_cell, assuming that the alter_cell file is in the current directory.