B Error and Alert Messages

This appendix lists the error and alert messages that can be occur when using Oracle Exadata System Software.

B.1 Understanding Alert, Incident, and Trace Files

Alert, incident, and trace files provide a diagnostic record of useful information. Alert files contain information about internal errors and administrative tasks. Incident files contain information about single occurrences. Trace files can contain information about server and background processes. This section contains the following topics:

B.1.1 About Alert Files

An alert file is a log file that records information about internal errors and administrative activities, such as backups.

When an internal error occurs, a message is sent to the terminal screen and is written to the alert file. Additional information about internal errors is also written to the alert file, such as the location and name of any trace files generated because of the error.

Alert files are located in the following directory:

/opt/oracle/cell/log/diag/asm/cell/hostname/trace/alert.log

If your system uses an operator console, then some messages from Oracle may appear on the console. All important messages are written to the alert file and the operator console. Because all messages, not just Oracle messages, appear on this console, the alert file is a better record for tracing all Oracle administrative activity and errors than the console log.

B.1.2 About Incidents and Incident Packages

An incident package is a collection of data about incidents for one or more problems.

An incident is a single occurrence of a problem. When a problem occurs multiple times, an incident is created for each occurrence. Incidents are tracked in the Automatic Diagnostic Repository (ADR). Each incident is identified by a numeric incident identifier, which is unique within ADR. When an incident occurs, the database makes an entry in the alert log, sends an incident alert to Oracle Enterprise Manager, gathers diagnostic data about the incident in the dump files (incident dumps), tags the incident dumps with the incident ID, and stores the incident dumps in the ADR subdirectory created for that incident.

Diagnosis and resolution of a critical error usually starts with an incident alert. You can obtain a list of all incidents in ADR using an ADR Command Interpreter (ADRCI) command.

Each incident is mapped to a single problem only. Incidents are compared so that a single problem does not generate too many incidents and incident dumps.

Before uploading diagnostic data to Oracle Support Services, you first collect the data into an intermediate logical structure called an incident package (package). A package is a collection of metadata that is stored in the ADR and that points to diagnostic data files and other files both in and out of the ADR. When you create a package, you select one or more problems to add to the package. The Support Workbench then automatically adds to the package the problem information, incident information, and diagnostic data (such as trace files and dumps) associated with the selected problems. Because a problem can have many incidents (many occurrences of the same problem), by default only the first three and last three incidents for each problem are added to the package, excluding any incidents that are over 90 days old. You can change these default numbers on the Incident Packaging Configuration page of the Support Workbench.

After the package is created, you can add any type of external file to the package, remove selected files from the package, or edit selected files in the package to remove sensitive data. As you add and remove package contents, only the package metadata is modified. When you are ready to upload the diagnostic data to Oracle Support Services, you first create a zip file that contains all the files referenced by the package metadata.

B.1.3 About Trace Files

A trace file is created each time an Oracle instance starts or an unexpected event occurs in a user process or background process.

The file extension or file type is usually .trc. If it is different, then it is noted in your operating system-specific Oracle documentation. The contents of the trace file may include dumps of the system global area, process global area, operating call stack, and registers.

Note:

If you change a traceLevel attribute setting, then you need to restart Management Server (MS) for the change to take effect. Restarting MS does not affect the database or the flow of data.

B.1.4 About Automatic Diagnostic Repository

The Automatic Diagnostic Repository (ADR) is a file-based repository for database diagnostic data such as traces, dumps, the alert log, health monitor reports, and more. It has a unified directory structure across multiple instances and multiple products.

The database, Oracle Automatic Storage Management (Oracle ASM), the listener, Oracle Clusterware, Oracle Exadata Storage Server, and other Oracle products or components store all diagnostic data in the ADR. Each instance of each product stores diagnostic data underneath its own home directory within the ADR. For example, in an Oracle Real Application Clusters (Oracle RAC) environment with shared storage and Oracle ASM, each database instance and each Oracle ASM instance has an ADR home directory. ADR's unified directory structure, consistent diagnostic data formats across products and instances, and a unified set of tools enable customers and Oracle Support Services to correlate and analyze diagnostic data across multiple instances. With Oracle Clusterware, each host node in the cluster has an ADR home directory.

Note:

Because all diagnostic data, including the alert log, are stored in the ADR, the initialization parameters BACKGROUND_DUMP_DEST and USER_DUMP_DEST are deprecated. They are replaced by the initialization parameter DIAGNOSTIC_DEST, which identifies the location of the ADR.
B.1.4.1 Automatic Diagnostic Repository Incident

ADR incidents are generated and stored in ADR by the Oracle diagnosability framework when Oracle encounters critical software errors. Incidents may have associated trace files and dump files that can be packaged together to send to Oracle Support Services.

B.1.4.2 Automatic Diagnostic Repository Package

An ADR package is a collection of ADR incidents, and their related trace and dump files organized into a single (compressed) file for transfer to Oracle Support Services.

B.1.4.3 Diagnostic File Locations

Alert, incident, and trace files are written to the alert, incident, and trace subdirectories in the ADR home directory ($ADR_BASE/diag/asm/cell/cell_name) on the cell. The ADR home is located within the ADR base directory ($ADR_BASE). The retention period for ADR files is specified by the diagHistoryDays cell attribute. You can modify this setting with the CellCLI ALTER CELL command.

If you use Secure Shell (SSH) to access the cell, then you can display the value of $ADR_BASE that was set during installation.

Related Topics

B.1.5 Managing Diagnostic Files

ADR Command Interpreter (ADRCI) is a command-line tool that you use to manage diagnostic data collected by ADR Command Interpreter (ADRCI).

Using ADRCI, you can perform the following duties:

  • View diagnostic data within ADR

  • Package incident and problem information into a zip file for transmission to Oracle Support Services

In order to use ADRCI with Oracle Exadata System Software, set the ADR base using the following command:

ADRCI> SET BASE /opt/oracle/cell/log

With ADRCI you can view the alert, incident, and trace files for a cell, as shown in the following example.

Example B-1 Viewing Alert, Incident, and Trace Files

$ ADRCI
ADRCI: Release 11.2.0.1.0 - Production on Wed May 20 02:17:38 2009
Copyright (c) 1982, 2009, Oracle.  All rights reserved.

ADRCI> SET BASE /opt/oracle/cell/log

ADRCI> SHOW HOMES
ADR Homes:
diag/asm/cell/st-cell03-2
...

ADRCI> SET HOMEPATH diag/asm/cell/st-cell03-2

ADRCI> SHOW ALERT
...
ADRCI> SHOW INCIDENT
...
ADRCI> SHOW TRACEFILE
...

B.2 Oracle Exadata System Software Error Messages

The following categories of Oracle Exadata System Software error messages are described in this section:

B.2.1 Error Messages: CELL-00001 to CELL-00500

These error messages are in the range CELL-00001 through CELL-00500.

CELL-00001: Invalid date/time format. Please use a valid format, for example: {0}

Cause: An invalid date/time format was entered.

Action: Enter the date/time in a valid format, such as '2009-09-01T15:28:36-07:00'.

See Also:

  • Example 8-124 for an example of the use of the date/time format in a LIST command

  • "SET" for additional information about setting the default date/time format

CELL-00002: The ALTER IORMPLAN command contains an invalid level {0}.

Cause: An invalid level was entered in an IORMPLAN plan.

Action: Enter a level number from 1 to 8.

CELL-00003: The ALTER IORMPLAN command contains an invalid allocation {0}.

Cause: An invalid allocation value was entered in an IORMPLAN plan.

Action: Enter an allocation value from 0 to 100.

CELL-00004: The ALTER IORMPLAN command contains an invalid name {0}.

Cause: A name value was entered in an IORMPLAN plan that is a reserved word or contains too many characters.

Action: Enter a valid database or category name, or use other or emergency for the name.

CELL-00005: The ALTER IORMPLAN command contains too many {0} directives.

Cause: More than 32 directives were entered in an IORMPLAN plan.

Action: Enter a maximum of 32 directives for each dbPlan or catPlan category.

CELL-00006: The ALTER IORMPLAN command contains an invalid allocation total at level {0}.

Cause: The total of the allocation values at a given level exceeded 100.

Action: Enter allocation values such that the total of the allocation values at a given level does not exceed 100.

CELL-00007: The ALTER IORMPLAN command does not contain OTHER directive.

Cause: At least one directive with name=other was required for both the dbPlan and catPlan categories.

Action: Enter a directive with name=other for both the dbPlan and catPlan categories.

CELL-00010: This attribute requires 'true' or 'false' values: {0}

Cause: An incorrect value was entered for a Boolean attribute, such as the smtpstarttls cell attribute.

Action: Enter true or false for the value of the Boolean attribute.

See Also:

  • "ALTER" for additional information about altering attributes

  • "DESCRIBE" for lists of attributes that can be modified for each object type

CELL-00011: Maximum length exceeded for attribute: {0}

Cause: The value was longer than the attribute field allowed. For example, the text provided for the attribute value for name or the comment must be fewer than 256 characters.

Action: Enter a value equal to or less than the maximum length allowed for the attribute.

See Also:

"ALTER" for additional information about altering attributes
CELL-00012: Name value is not valid. ASCII characters a-zA-Z_0-9 required.

Cause: Invalid characters, such as asterisk (*) or percent (%), were entered for the name attribute value.

Action: Enter a name value that contains only ASCII alphanumeric and underscore characters.

CELL-00013: Attribute is not modifiable: {0}

Cause: The attribute could not be modified.

Action: Use DESCRIBE object_type to display a list of modifiable attributes for the specified object.

See Also:

"DESCRIBE"
CELL-00014: Object does not support this attribute: {0}

Cause: The specified attribute was not supported by the object type.

Action: Use DESCRIBE object_type to display a list of valid attributes for the specified object.

See Also:

"DESCRIBE"
CELL-00015: Attribute {0} must be set.

Cause: A value other than zero (0) was set for the attribute.

Action: Set the attribute to zero.

CELL-00016: The ALTER IORMPLAN command must specify values for both allocation and level attributes.

Cause: The IORMPLAN directive did not specify both the allocation attribute and level attribute.

Action: Specify both the allocation and level attributes for the directive.

See Also:

"ALTER IORMPLAN"
CELL-00018: The ALTER IORMPLAN command contains an invalid limit {0}.

Cause: An invalid limit value was specified for the IORMPLAN directive.

Action: Specify a valid limit.

See Also:

"ALTER IORMPLAN"
CELL-00019: The limit attribute is not permitted on catplan directives.

Cause: The limit attribute was used in a catPlan directive.

Action: Remove the limit attribute from the catPlan directive.

See Also:

"ALTER IORMPLAN"
CELL-00020: The ALTER IORMPLAN command must specify at least one of the following attributes: allocation, share, limit, flashcache flashlog, flashCachelimit, flashCacheSize, or flashCacheMin.

Cause: The IORMPLAN directive did not specify the correct value or attribute.

Action: Specify the following for the directive:

  • an allocation, share or limit value

  • flash cache or flash log attribute

  • flash cache limit or flash cache minimum

See Also:

"ALTER IORMPLAN"
CELL-00021: The ALTER IORMPLAN command cannot specify values for both allocation and share attributes.

Cause: The IORMPLAN directive specified both an allocation value and a share value.

Action: Specify only one value for the directive.

See Also:

"ALTER IORMPLAN"
CELL-00022: The IORMPLAN cannot have OTHER directive in a share-based plan.

Cause: A share-based plan included the OTHER directive.

Action: Remove the OTHER directive from the share-based plan.

See Also:

"ALTER IORMPLAN"
CELL-00023: The IORMPLAN contains an invalid value {0} for share. Share must be assigned an integer from 1 to 32.

Cause: An invalid value was specified for the share value.

Action: Only integers from 1 to 32 are valid for a share value. Enter a valid value.

See Also:

"ALTER IORMPLAN"
CELL-00024: The IORMPLAN total share value {0} is too large. The sum of all shares cannot be greater than 32768.

Cause: The sum of the share values exceed the 32768 limit.

Action: Change share values to be equal or less than 32768.

See Also:

"ALTER IORMPLAN"
CELL-00025: The ALTER IORMPLAN command DEFAULT is a reserved word, and cannot specify role, asmcluster, level or allocation

Cause: Issued an ALTER IORMPLAN command and specified role, asmcluster, level, or allocation for default.

Action: Reattempt the command and provide the correct values.

See Also:

"ALTER IORMPLAN"
CELL-00026: The ALTER IORMPLAN command cannot have more than 32 directives with level and allocation attributes.

Cause: The IORMPLAN command included more than 32 directives with level and allocation attributes.

Action: Change the number of directives and attributes for the IORM plan.

See Also:

"ALTER IORMPLAN"
CELL-00027: The sum of the flashCacheMin and flashCacheSize directives in the ALTER IORMPLAN command cannot be greater than the current flashcache size: {0}.

Cause: The total size of the flashcachemin directives was greater than the current size of flash cache.

Action: Set the flashcachemin directive sizes to be less than the total flash cache size.

CELL-00028: The ALTER IORMPLAN command cannot have flashCacheMin, flashCacheSize, or flashCacheLimit attributes for the OTHER directive.

Cause: The OTHER directive included flashcachemin or flashcachelimit.

Action: Remove the flashcachemin or flashcachelimit from the OTHER directive.

CELL-00029: Invalid value for email: {0}.

Cause: An invalid value was entered for the email option.

Action: Specify a valid e-mail address for the ALTER CELL emailSubscriber command.

CELL-00030: Invalid value for alertType: {0}.

Cause: An invalid value was entered for the alterType option.

Action: Specify a valid option for the ALTER CELL emailSubscriber command. Valid options are HARDWARE, SOFTWARE, METRIC, and ADR.

CELL-00031: The ALTER IORMPLAN command should have both primary and standby directives for database {0}.

Cause: The database plan did not include the primary and standby directives.

Action: Re-enter the ALTER IORMPLAN command, and specify both directives in the database plan.

CELL-00032: The catplan cannot be set when dbplan has profile type directives.

Cause: The catPlan parameter was not set because the dbplan parameter included the profile type directive.

Action: There are two actions for this error message. The actions are as follows:

  • Clear the dbPlan or remove the profile directives from the database plan, and then set the catPlan parameter.

    ALTER IORMPLAN dbPlan = ''
    ALTER IORMPLAN catPlan = parameter_settings
    
  • Remove profile directives from the database plan. This allows the use of the dbPlan parameter with the catPlan par amber.

CELL-00033: Profile type directives cannot be specified in IORMPLAN dbplan when catplan is active.

Cause: The dbPlan parameter included the profile type directive, but the catPlan parameter was active.

Action: Clear the catPlan, and then set the profile directives for the database plan.

ALTER IORMPLAN catPlan = ''
ALTER IORMPLAN dbPlan = parameter_settings
CELL-00034: The ALTER IORMPLAN command contains too many {0} directives.

Cause: The ALTER IORMPLAN command contained too many of the specified directives.

Action: Limit the number of directives to 8 for type= profile directives, and 1023 for database directives.

CELL-00035: The ALTER IORMPLAN command cannot specify flashCacheSize if flashCacheMin or flashCacheLimit is specified.

Cause: The flashCacheMin, flashCacheLimit, and flashCacheSize attributes cannot be specified for category plans.

Action: Use either the flashCacheSize attribute to specify a guaranteed hard limit, or the flashCacheMin or flashCacheLimit attributes to specify a soft limit.

CELL-00036: Invalid start time format. Required format: yyyy_MM_ddTHH_mm_ss or 'now'.

Cause:An invalid time format was specified for the CREATE DIAGPACK command.

Action: Specify the time using the format yyyy_MM_ddTHH_mm_ss or using the keyword now. For example, CREATE DIAGPACK packStartTime="2017_04_16T15_00_00".

CELL-00047: The {0} attribute is not permitted when specifying catplan directives.

Cause: Issued an ALTER IORMPLAN command and attempted to specify an unsupported attribute.

Action: Reattempt the command and remove the unsupported attributes.

CELL-00048: The {0} attribute is not permitted when specifying dbplan "{1}" directives.

Cause: Issued an ALTER IORMPLAN command and attempted to specify an unsupported attribute.

Action: Reattempt the command and remove the unsupported attributes.

CELL-00049: The ALTER IORMPLAN command cannot specify a value for the {0} attribute if the attribute {1} is also specified.

Cause: Issued an ALTER IORMPLAN command and attempted to specify an unsupported attribute.

Action: Reattempt the command and provide the correct values.

CELL-00051: SNMP V3 user definition “{0}” must include authProtocol and authPassword.

Cause: The user definition did not include the authProtocol and authPassword.

Action: Enter the command to define the SNMP user, and specify the authProtocol and authPassword.

CELL-00052: SNMP V3 user definition “{0}” authentication passwords must contain at least 8 and at most 12 alphanumeric characters. Privacy passwords must contain exactly 8 alphanumeric characters.

Cause: The password did not contain the correct amount of characters.

Action: Enter a password that has the correct amount of characters. SNMP v3 passwords must be at least 8 and at most 12 alphanumeric characters. Encryption passwords must contain exactly 8 alphanumeric characters.

CELL-00053: SNMP V3 user definition “{0}” is defined more than once.

Cause: The user definition was already defined.

Action: Define a new user.

CELL-00054: SNMP V3 user definition “{0}” contains privProtocol, but no privPassword.

Cause: The user definition did not include a password.

Action: Enter the definition, and include a password.

CELL-00055: SNMP V3 user definition “{0}” cannot be removed because it is referenced by an SNMP v3 subscription.

Cause: The definition could not be removed.

Action: Re-enter the command after removing the subscription.

CELL-00056: SNMP V3 snmpUser definition can only be used for subscriptions that are type V3 or V3ASR.

Cause: The user definition did not specify a type.

Action: Enter the definition, and specify subscription type V3 or v3ASR.

CELL-00057: Invalid protocol specified for {0}. This protocol value must be either {1} or {2}.

Cause: An invalid protocol was specified.

Action: Re-enter the command with the correct protocol value.

CELL-00058: The specified directive contains repeated attributes: {0}. A single occurrence of an attribute is allowed in each directive.

Cause: An attribute was repeated in the directive.

Action: Enter the command, and specify each attribute only once.

CELL-00059: The snmpSubscriber directive includes an invalid type. Only types ASR, V3, and V3ASR are allowed. The default type is V1.

Cause: The snmpSubscriber directive included an invalid type.

Action: Enter the command, and specify a valid type. Valid types are ASR, V3, and v3ASR.

CELL-00060: SNMP V3 user definition “{0}” contains privPassword, but no privProtocol.

Cause: The user definition did not include the protocol.

Action: Enter the command, and specify the protocol.

CELL-00061: SNMP V3 subscriptions require that an SNMP user is defined, and is referenced by name using the snmpUser directive in the snmpSubscriber attribute assignment.

Cause: The snmpSubscriber had type V3 or v3ASR specified, but it did not include an snmpUser attribute.

Action: Re-enter the command, and include snmpUser in the definition, or change the type of snmpSubscriber to not specify V3.

CELL-00062: The SNMP subscription references an SNMP user, {0}, that is not is defined. It should be defined using the snmpUser attribute assignment.

Cause: The SNMP user referenced in the subscription is not defined.

Action: Define the user for the subscription.

CELL-00063: The SNMP user name is invalid. It must be 1 to 32 alphanumeric characters.

Cause: An invalid user name was entered.

Action: Enter the user name using 1 to 32 alphanumeric characters.

CELL-00064: This operation cannot be performed at this time due to conflicting startup activity on ILOM. Re-enter this command in a few minutes.

Cause: There was a conflicting activity.

Action: Re-enter the command after a few minutes.

CELL-00065: This SNMP engine id change would invalidate existing SNMP user definitions. Use the ALTER command to remove SNMP users, and then change the SNMP engine id. The SNMP user definitions must then be re-created.

Cause: The engine identifier change was not done due to existing user definitions.

Action: Remove the SNMP users, then change the SNMP engine identifier, and then re-create the user definitions.

CELL-00066: This command requires password input, but is not being run in an interactive mode which would allow this input.

Cause: The command failed because CLI was not run in interactive mode.

Action: Run the CLI program from a local shell.

CELL-00067: The second password does not match the first.

Cause: The confirmation password did not match the original password.

Action: Re-enter the confirmation password.

CELL-00072: SNMP community name may not contain spaces or the following characters: = ’ ” \ / < >

Cause: The snmpSubscriber value specified contains a community name with one or more disallowed characters.

Action: Fix the command by removing the disallowed characters from the community name.

CELL-00075: A scheduled software update for {0} is already running.

Cause: You attempted to schedule a software update, but there is already a software update running.

Action: Wait for the current software update to complete.

CELL-00076: An error occurred during download of software update: {0}

Cause: There was a problem when attempting to download the software update.

Action: See the additional error message for details.

CELL-00077: An error occurred during prerequisite check for software update: {0}

Cause:

Action:

CELL-00078: An error occurred during upgrade of software: {0}

Cause: The specified URL or patch file was not found.

Action:

CELL-00079: SoftwareUpdate {0} attribute must be specified as a future date and time.

Cause: The date and time was specified for the software update that is before the current time.

Action: Specify a date and time for the software update that is in the future.

CELL-00080: SoftwareUpdate {0} attribute must contain a valid URL.

Cause:

Action:

CELL-00081: SoftwareUpdate {0} attribute must contain a valid frequency. It should be daily, weekly, biweekly. or none.

Cause:

Action:

CELL-00082: SoftwareUpdate name can only be set to a version in the SoftwareUpdate store. The store attribute must be set to a URL of a store containing valid software updates.

Cause:

Action:

CELL-00083: SoftwareUpdate name can only be set to a version in the SoftwareUpdate store. The current store contains the following versions: {0}

Cause:

Action:

CELL-00084: SoftwareUpdate version {0} is already installed.

Cause:

Action:

CELL-00085: SoftwareUpdate history does not exist for update {0}.

Cause:

Action:

CELL-00086: There is not enough available space on this Exadata Storage Server file systems for the software update. A minimum of {0}M for the ZIP file is temporarily required on either root, /var/log/oracle or /opt/oracle file systems. The available space on the root file system is {1}M, and from that space {2}M is required for applying the update. The available space on the /var/log/oracle file system is {3}M. The available space on the /opt/oracle file system is {4}M.

Cause: There is not enough available disk space to store the software update

Action: Make more disk space available and schedule the software update again.

CELL-00087: There is not enough available space on this Exadata Storage Server root file system for the software update. The available space on the root file system is {0}M. The software update will require at least {1}M on the root file system. An additional {2}M for the ZIP file will be needed temporarily on root, /var/log/oracle or /opt/oracle file systems.

Cause: There is not enough available disk space to store the software update.

Action: Make more disk space available and schedule the software update again.

CELL-00088: Cell validations cannot be run while software update is in progress. Wait until update completes to run this command.

Cause:

Action:

CELL-00089: Failed to connect to host at store url: {0}.

Cause:

Action:

CELL-00090: The URL is malformed. The syntax is not correct.

Cause:

Action:

CELL-00091: The store's TLS certificate is not valid.

Cause:

Action:

CELL-00092: The store's TLS certificate cannot be authenticated with known CA certificates.

Cause:

Action:

CELL-00093: The SoftwareUpdate store attribute must be set to a valid URL before the time attribute is set.

Cause:

Action:

CELL-00094: The software update files were not found on the store server. Verify that the SoftwareUpdate store attribute value is correct.

Cause:

Action:

CELL-00095: This command must be run in interactive mode or with the FORCE option.

Cause:

Action:

CELL-00097: The syslogFormat value cannot contain control characters. If a control character is needed, it should be preceded by a backslash ('\') character.

Cause: The syslogFormat value specified contains a control character.

Action: Retry command with a backslash character preceding the control character.

CELL-00098: The syslogFormat attribute cannot be changed because the existing syslog configuration is not standard. Contact Oracle Support Services.

Cause: The rsyslog.conf file could not be found or thersyslog.conf file does not contain the expected format.

Action: Contact Oracle Support Services for assistance.

CELL-00099: Changing password through REST services is not allowed. Contact the administrator of server {0} to change the password.

Cause: You issued a REST command to change the user password.

Action: You cannot change the user password through REST services. Contact the server administrator to change the password.

CELL-00100: Invalid user password expiration time specified for pwdExpInDays. Specify the expiration time in days. For example, to set the password expiration time to 60 days: alter [cell | dbserver] pwdExpInDays = 60

Cause: An invalid value was specified for the password expiration time.

Action: Specify the expiration time in days, as a positive integer.

CELL-00101: Invalid user password expiration warning time specified for pwdExpWarnInDays. Specify the expiration warning time in days. For example, to set the password expiration time to 7 days: alter [cell | dbserver] pwdExpWarnInDays= 7

Cause: An invalid value was specified for the password warning expiration time.

Action: Specify the expiration warning time in days, as a positive integer.

CELL-00102: Invalid user account lock time specified for accountLockInDays. Specify the account lock time in days. For example, to set the account lock time to 7 days: alter [cell | dbserver] accountLockInDays=7

Cause: An invalid value was specified for accountLockInDays.

Action: Specify the expiration time in days, as a positive integer.

B.2.2 Error Messages: CELL-00501 to CELL-01000

These error messages are in the range CELL-00501 through CELL-01000.

CELL-00501: Invalid syntax for powercount attribute. Error: {0}

Cause: IPMI/ILO produced unexpected output.

Action: Contact Oracle Support Services.

CELL-00502: Cannot parse temp limits. Error: {0}

Cause: IPMI/ILO produced unexpected output.

Action: Contact Oracle Support Services.

CELL-00503: Invalid syntax for fancount attribute. Error: {0}

Cause: The syntax for the fanCount attribute was invalid.

Action: Contact Oracle Support Services.

CELL-00506: Call updateHealth first.

Cause: A program error occurred.

Action: Contact Oracle Support Services.

CELL-00507: HardwareImpl could not be instantiated: {0}

Cause: IPMI/ILO produced unexpected output.

Action: Contact Oracle Support Services.

CELL-00508: Reseting LO100 BMC requires that Linux is rebooted. Command ignored since it will make the cell unavailable for some time. If you would like to perform the operation still, run the following commands as user root: ipmitool mc reset cold reboot

Cause: Cannot reset LO100 on DL180 G5 hardware because it leads to incorrect sensor readings and thresholds when the server is not rebooted after the BMC is reset.

Action: If you would like to reset BMC, then run the following commands as the root user. You may have to set the Oracle ASM disks to online on the cell when the cell comes back after the reboot with Oracle Exadata System Software earlier than 11g Release 2 (11.2).

ipmitool mc reset cold
reboot
CELL-00509: Cannot turn off cell Do-Not-Service LED because servicing the cell now could compromise data redundancy. The cell Do-Not-Service LED will automatically be turned off when data redundancy is fully restored.

Cause: Attempted to turn off the DoNotServiceLED.

Action: Wait until the DoNotServiceLED is turned off automatically.

CELL-00510: Do-Not-Service LED is not present on {0}.

Cause: Attempted to turn off the DoNotServiceLED on a system that does not have a DoNotServiceLED.

Action: The DoNotServiceLED is available on X7 and later systems.

B.2.3 Error Messages: CELL-01001 to CELL-01500

These error messages are in the range CELL-01001 through CELL-01500.

CELL-01005: Error in BMC adapter: {0}

Cause: A problem occurred with the BMC adapter.

Action: Contact Oracle Support Services.

B.2.4 Error Messages: CELL-01501 to CELL-02000

These error messages are in the range CELL-01501 through CELL-02000.

CELL-01501: Error spooling to file: {0}

Cause: The SPOOL command could not write to the specified file.

Action: Ensure that you have permissions to write to the file and to the directory.

See Also:

"SPOOL"

CELL-01502: Error accessing file: {0}

Cause: The file could not be found.

Action: Check that the file exists in the specified location.

See Also:

"SPOOL"

CELL-01503: File {0} already exists.

Cause: The spool file already exists so it could not be created.

Action: Specify the REPLACE option with the SPOOL command to overwrite an existing file, or specify the APPEND option with the SPOOL command to add to an existing file.

See Also:

"SPOOL"

CELL-01504: Invalid command syntax.

Cause: The command had a syntax error.

Action: Check the help text for the valid command syntax. The caret (^) character points to the location in the command where the error was detected.

See Also:

"HELP"

CELL-01505: The Restart Server (RS) is not running, so the state of Management Server (MS) or Cell Server (CELLSRV) is unknown.

Cause: Restart Server (RS) was not running.

Action: Start or restart the Restart Server with the ALTER CELL command.

See Also:

"ALTER CELL"

CELL-01506: No response from Restart Server (RS).

Cause: Restart Server (RS) was not available.

Action: Start or restart the Restart Server with the ALTER CELL command.

See Also:

"ALTER CELL"

CELL-01507: Cannot talk to the Restart Server (RS). Error: {0}

Cause: Restart Server (RS) was not available.

Action: Start or restart the Restart Server with the ALTER CELL command.

See Also:

"ALTER CELL"

CELL-01508: Restart Server (RS) is not running. Ensure that RS is running before requesting other 'ALTER CELL SERVICE' commands. {0}

Cause: Restart Server (RS) was not running.

Action: Start or restart the Restart Server with the ALTER CELL command.

See Also:

"ALTER CELL"

CELL-01509: Restart Server (RS) is not responding.

Cause: Restart Server (RS) was not available.

Action: Start or restart the Restart Server with the ALTER CELL command.

See Also:

"ALTER CELL"

CELL-01510: Cannot start a new Restart Server (RS) at port number: {0}. An instance of RS might be already running.

Cause: Restart Server (RS) could not be started with the specified port number.

Action: Contact Oracle Support Services.

CELL-01512: Cannot start a new Restart Server (RS). Exception received: {0}

Cause: A new Restart Server (RS) could not be started.

Action: Contact Oracle Support Services.

CELL-01513: CellCLI request to Restart Server (RS) has timed out.

Cause: The CellCLI request to Restart Server was not successful because it timed out.

Action: Contact Oracle Support Services.

CELL-01514: Connect Error. Verify that Management Server is listening at the specified HTTP port: {0}.

Cause: A problem occurred with the connection to the Management Server (MS).

Action: Contact Oracle Support Services.

CELL-01515: Unable to retrieve CellCLI process ID.

Cause: A problem occurred when running the CellCLI utility.

Action: Contact Oracle Support Services.

CELL-01516: Exception occurred in setup of CellCLI: {0}.

Cause: A problem occurred when configuring the CellCLI utility.

Action: Contact Oracle Support Services.

CELL-01517: Cannot start Restart Server (RS). The operation timed out.

Cause: Restart Server (RS) could not be started.

Action: Contact Oracle Support Services.

CELL-01518: Stop CELLSRV. Create Cell cannot continue with CELLSRV running.

Cause: The cell could not be created when Cell Server (CELLSRV) was running.

Action: Contact Oracle Support Services.

CELL-01519: Cannot talk to the Management Server (MS). Error: {0}

Cause: A problem occurred when configuring the CellCLI utility.

Action: Contact Oracle Support Services.

CELL-01520: This command is not permitted in monitor mode.

Cause: The CellCLI utility was run in monitor mode. This mode is intended for read-only users. Commands other than LIST are not allowed. This error indicates that an ALTER, CREATE, or DROP command was issued.

Action: Run the CellCLI utility in regular mode to issue commands that update CellCLI objects.

CELL-01521: Only ASCII text can be used in CellCLI commands.

Cause: Non-ASCII text was entered in a CellCLI command.

Action: Enter the command with ASCII text only.

CELL-01522: CALIBRATE must be run as the root user id.

Cause: You were not logged into the cell as the root user.

Action: Exit the CellCLI utility. Log out of the cell, and then log in as the root user, and run CALIBRATE.

CELL-01523: CALIBRATE should not run while CELLSRV is running. Stop CELLSRV or enter CALIBRATE FORCE.

Cause: Oracle Storage Server was running on the cell.

Action: Shut down Oracle Storage Server with ALTER CELL SHUTDOWN SERVICES CELLSRV, and then run CALIBRATE again.

See Also:

"ALTER CELL"

CELL-01524: An error occurred while running CALIBRATE tests.

Cause: An internal error occurred.

Action: Check the error that is detailed in the $LOG_HOME/cellcli.lst log file, then contact Oracle Support Services.

CELL-01525: An error occurred while running CALIBRATE tests on LUN {0}.

Cause: An internal error occurred.

Action: Check the error that is detailed in the $LOG_HOME/cellcli.lst log file, then contact Oracle Support Services.

CELL-01526: Local hostname mapping is inconsistent. Verify cell /etc/hosts file content.

Cause: The cell was unable to ping the host name because of a network configuration error.

Action: The /etc/hosts file should be examined to verify that the host name of the cell is mapped to an IP address which is valid for the cell. Correct any errors, then verify that the host name can be pinged successfully before starting the cell services.

CELL-01527: CALIBRATE did not find any LUNs that qualified for measurement.

Cause: No LUNs were found that were in the normal operating state and had a valid size.

Action: Use the LIST LUN DETAIL command to retrieve data about the LUN, then determine the reason for the invalid LUN status.

See Also:

"LIST LUN"

CELL-01528: Unable to create the log file in directory {0}. Error: {1}.

Cause: Permissions for the directory or the file do not allow the CellCLI log file to be written. The error should be checked to diagnose the problem. The CellCLI utility continues to work using the default logging configuration.

Action: Correct the error indicated in the directory.

CELL-01529: Cannot start a new Restart Server (RS). No space available on cell file systems. Remove files to free space on the cell file systems mounted on '/'and '/opt/oracle'.

Cause: There was no space on the cell file system.

Action: Remove files from the / and /opt/oracle directories to make space.

CELL-01530: Invalid WHERE clause usage. The WHERE clause is supported only for LIST commands.

Cause: The WHERE clause was used incorrectly with a CellCLI command.

Action: The WHERE clause is only supported for use with the LIST command. Remove the WHERE clause from the current command.

CELL-01533: Unable to validate the IP addresses from the cellinit.ora file because IP may be down or misconfigured.

Cause: The cellinit.ora file contained invalid IP addresses.

Action: Correct the problem, and restart CELLSRV. If that does not correct the problem, then contact Oracle Support Services.

CELL-01537: Unable to read the cell_disk_config.xml file because the file may be missing or empty.

Cause: The cell_disk_config.xml file could not be read.

Action: Contact Oracle Support Services.

CELL-01544: Could not create the $OSSCONF/flashlog directory.

Cause: The $OSSCONF/flashlog directory could not be created.

Action: Contact Oracle Support Services.

CELL-01545: Could not create the $OSSCONF/flashlog/savedredo directory.

Cause: The $OSSCONF/flashlog/savedredo directory could not be created.

Action: Contact Oracle Support Services.

CELL-01547: CELLSRV startup failed due to unknown reasons.

Cause: CELLSRV startup failed.

Action: Contact Oracle Support Services.

CELL-01548: Unable to shut down CELLSRV because disk group CONTROLFILE, DATAFILE, LOGFILE may be forced to dismount due to reduced redundanc

Cause: CELLSRV did not shutdown because the disk group may dismount.

Action: Contact Oracle Support Services.

CELL-01549: CELLSRV shutdown failed because Oracle ASM is not responding.

Cause: CELLSRV did not shut down because Oracle ASM did not respond.

Action: Contact Oracle Support Services.

CELL-01550: CELLSRV shutdown failed because CELLSRV is not responding.

Cause: CELLSRV was not responding.

Action: Contact Oracle Support Services.

CELL-01551: Cannot connect to CELLSRV.

Cause: The system could not connect to CELLSRV.

Action: Contact Oracle Support Services.

CELL-01553: Incorrect IP in cellinit.ora. IP is invalid or has incorrect/missing netmask. Please refer to RS incident log.

Cause: An incorrect IP address was in the cellinit.ora file.

Action: Correct the problem, and then restart CELLSRV. If that does not correct the problem, then contact Oracle Support Services.

CELL-01554: MS startup failed for unknown reasons.

Cause: An internal error occurred.

Action: Contact Oracle Support Services.

CELL-01555: RS startup failed for unknown reasons.

Cause: An internal error occurred.

Action: Contact Oracle Support Services.

CELL-01556: CELLSRV shutdown failed for unknown reasons..

Cause: An internal error occurred.

Action: Contact Oracle Support Services.

CELL-01557: MS shutdown failed for unknown reasons.

Cause: An internal error occurred.

Action: Contact Oracle Support Services.

CELL-01558: RS shutdown failed for unknown reasons.

Cause: An internal error occurred.

Action: Contact Oracle Support Services.

CELL-01559: Failure for unknown reasons.

Cause: An internal error occurred.

Action: Contact Oracle Support Services.

B.2.5 Error Messages: CELL-02001 to CELL-02500

These error messages are in the range CELL-02001 through CELL-02500.

CELL-02001: Object name expected.

Cause: An object name was not entered with the command.

Action: Enter the object name with the CellCLI command.

See Also:

"LIST CELLDISK"

CELL-02002: Unexpected object in list for LIST.

Cause: An invalid object was entered with the LIST command.

Action: Use DESCRIBE object_type to display a list of valid attributes for the specified object. Check the Help text for the valid command syntax.

See Also:

CELL-02004: Cell object filtering is not supported with CellCLI commands.

Cause: Filtering could not be performed on the cell.

Action: Enter the LIST CELL command without a filtering clause.

See Also:

"LIST CELLDISK"

CELL-02005: Invalid command.

Cause: There was an invalid command-object combination, such as DROP CELL or ALTER PHYSICALDISK.

Action: Check the help text for the valid command syntax.

See Also:

"HELP"

CELL-02006: Physical disk does not exist: {0}. Please use 'LIST PHYSICALDISK' to see valid disk names.

Cause: The name provided did not match any existing physical disks.

Action: Use the LIST PHYSICALDISK command to display the names of the existing physical disks.

See Also:

"LIST PHYSICALDISK"

CELL-02007: Grid disk does not exist: {0}

Cause: The name provided did not match any existing grid disks.

Action: Use the LIST GRIDDISK command to display the names of the existing grid disks.

See Also:

"LIST GRIDDISK"

CELL-02008: LUN does not exist: {0}. Please use 'LIST LUN' to see valid LUN names.

Cause: The name provided did not match any existing LUNs.

Action: Use the LIST LUN command to display the names of the existing LUNs.

See Also:

"LIST LUN"

CELL-02010: Metric definition does not exist: {0}

Cause: The name provided does not match any existing metric definitions.

Action: Use the LIST METRICDEFINITION command to display the names of the existing metric definitions.

See Also:

"LIST METRICDEFINITION"

CELL-02011: Key does not exist for client: {0}.

Cause: The security key did not exist for the client.

Action: Use the LIST KEY command to display the known client names and keys, and then use the correct client name.

CELL-02012: ACTIVEREQUEST does not exist: <active_request>

Cause: The name provided did not match any existing active requests.

Action: Use the LIST ACTIVEREQUEST command to display the names of the existing active requests.

See Also:

"LIST ACTIVEREQUEST"

CELL-02013: Alert definition does not exist: {0}

Cause: The name provided did not match any existing alert definitions.

Action: Use the LIST ALERTDEFINITION command to display the names of the existing alert definitions.

See Also:

"LIST ALERTDEFINITION"

CELL-02014: Invalid object type.

Cause: An invalid object type was specified.

Action: Enter a valid object type with the CellCLI command.

CELL-02015: Alert does not exist: {0}

Cause: An alert named in LIST ALERTHISTORY did not exist.

Action: Use the LIST ALERTHISTORY command to display the names of the existing alerts.

See Also:

"LIST ALERTHISTORY"

CELL-02016: Metric does not exist: {0}

Cause: A metric named in LIST METRICHISTORY did not exist.

Action: Use the LIST METRICDEFINITION command to display the names of the existing metrics.

See Also:

"LIST METRICDEFINITION"

CELL-02018: Internal error detected: {0}

Cause: An internal error occurred.

Action: Contact Oracle Support Services.

CELL-02019: Internal CLI/MS version error. MS expected {0}, but CLI sent {1}.

Cause: An internal error occurred.

Action: Contact Oracle Support Services.

CELL-02020: InfiniBand Port {0} does not exist.

Cause: The name provided did not match any existing InfiniBand ports.

Action: Use the LIST IBPORT command to display the InfiniBand port names.

CELL-02021: No metric data found.

Cause: The metric specified in the LIST METRICCURRENT command was not in the current in-memory collected metrics.

Action: This message is informational. No action is needed.

CELL-02023: Database {0} specified by the LIST command does not exist.

Cause: The database specified by the command did not exist.

Action: Check the database name, and retry the command.

CELL-02024: The LIMIT value cannot exceed {0} for the LIST command when using the ORDER BY option.

Cause: The LIMIT value exceeded the allowed amount for long-running commands.

Action: Enter a lower value for the LIMIT value.

CELL-02025: The LIMIT parameter is mandatory for LIST command when using the ORDER BY option.

Cause: The LIMIT parameter was not included in the command.

Action: Include the LIMIT parameter with the command when using the ORDER BY option.

CELL-02026: The LIMIT value must be a positive integer.

Cause: The LIMIT value was not a positive integer.

Action: Enter the command using a positive integer for the LIMIT value.

B.2.6 Error Messages: CELL-02501 to CELL-03000

These error messages are in the range CELL-02501 through CELL-03000.

CELL-02501: Pre-existing ALERTDEFINITION: {0}

Cause: An internal error occurred. Alert definitions could not be added or renamed.

Action: Contact Oracle Support Services.

CELL-02503: Invalid operation.

Cause: This generic error message displayed because invalid command syntax, such as DROP CELL or ALTER CELL INACTIVE, was entered.

Action: Check the Help text for the valid command syntax.

See Also:

HELP
CELL-02504: Invalid IP address format.

Cause: An invalid string was entered for the IP address value.

Action: Enter the IP address in the valid Classless Inter-Domain Routing (CIDR) format: ip1.ip2.ip2.ip4/bitmask.

For example:

172.16.201.232/21
CELL-02505: Invalid number value for attribute: {0}

Cause: An invalid number was entered, such as a negative number.

Action: Enter a valid number. For example, enter a positive integer for the SMTP port number.

See Also:

ALTER CELL
CELL-02508: Error writing the configuration file. Error: {0}

Cause: The configuration file on the cell could not be written to.

Action: Check the write permissions on the configuration file and directory. For example, ensure that it is possible to write to the cellinit.ora file on the cell.

CELL-02509: The 'ALTER CELL ONLINE/OFFLINE' command option is not supported.

Cause: The cell could not be taken online or offline.

Action: No action is required. The cell is online by default.

CELL-02512: There was an error setting event: {0}

Cause: This error may occur when Management Server (MS) could not communicate properly with Cell Server (CELLSRV).

Action: Restart CELLSRV with the ALTER CELL command.

See Also:

ALTER CELL
CELL-02513: There is a communication error between MS and CELLSRV while getting event: {0}

Cause: This error could occur when Management Server (MS) could not communicate properly with Cell Server (CELLSRV).

Action: Restart CELLSRV with the ALTER CELL command.

See Also:

ALTER CELL
CELL-02518: Either LUN or PHYSICALDISK, but not both, is required to create a cell disk.

Cause: Both the lun and physicalDisk attribute values were specified when creating a cell disk.

Action: Specify either the lun or physicalDisk attribute value when creating a named cell disk.

See Also:

CREATE CELLDISK
CELL-02522: Celldisk attribute required.

Cause: No value was entered for the cellDisk attribute in a CREATE GRIDDISK command.

Action: Enter a valid name for the cellDisk attribute.

See Also:

CREATE GRIDDISK
CELL-02523: Celldisk name is invalid.

Cause: An invalid name was entered for the cellDisk attribute.

Action: Enter a valid name for the cellDisk attribute. Use LIST CELLDISK to display valid cell disk names.

CELL-02524: Cell Server (CELLSRV) cannot successfully add grid disk: {0}

Cause: Either Cell Server (CELLSRV) failed or some other indication of the problem was included with the error message.

Action: Restart CELLSRV with the ALTER CELL command.

See Also:

ALTER CELL
CELL-02525: Unknown cell disk: {0}

Cause: The specified cell disk in the CellCLI command did not exist.

Action: Use LIST CELLDISK to display existing cell disks, then re-enter the command with an existing cell disk name.

See Also:

LIST CELLDISK
CELL-02526: Preexisting cell disk: {0}

Cause: A new cell disk could not be created with the name of an existing cell disk.

Action: Use LIST CELLDISK to display existing cell disks, then re-enter the command with a unique cell disk name that does not already exit.

See Also:

LIST CELLDISK
CELL-02528: Pre-existing grid disk: {0}

Cause: A new grid disk could not be created with the name of an existing grid disk.

Action: Use LIST GRIDDISK to display existing grid disks, then re-enter the command with a unique grid disk name that does not already exist.

See Also:

LIST GRIDDISK
CELL-02529: CREATE command is not applicable to metric definitions.

Cause: Metric definitions could not be created with the CellCLI CREATE command.

Action: No action is required.

CELL-02531: CREATE command is not applicable to alert definitions.

Cause: Alert definitions could not be created with the CellCLI CREATE command.

Action: No action is required.

CELL-02532: ALTER command is not applicable to alert definitions.

Cause: Alert definitions could not be altered with the CellCLI ALTER command.

Action: No action is required.

CELL-02534: The command has not been implemented.

Cause: The specified CellCLI command is not supported in this release.

Action: No action is required.

CELL-02539: Cannot get cell disk GUIDs from Cell Server (CELLSRV) during initial Management Server (MS) - CELLSRV synchronization.

Cause: An internal error occurred.

Action: Contact Oracle Support Services.

CELL-02540: Cannot get cell disk information from Cell Server (CELLSRV) for cell disk GUID: {0}

Cause: An internal error occurred.

Action: Contact Oracle Support Services.

CELL-02541: Cannot get grid disk GUIDs from Cell Server (CELLSRV).

Cause: An internal error occurred.

Action: Contact Oracle Support Services.

CELL-02542: Cannot get grid disk information from Cell Server (CELLSRV).

Cause: An internal error occurred.

Action: Contact Oracle Support Services.

CELL-02543: Cannot locate LUN for cell disk: {0}, partition: {1}

Cause: During Management Server (MS) start up, MS could not synchronize the cell disk information with information that was on the disks because the LUN had disappeared since the cell disks were created.

Action: Identify the missing LUN and diagnose the cell disk.

CELL-02544: Invalid IORMPLAN attribute list.

Cause: An invalid attribute was specified in a CellCLI command.

Action: Use DESCRIBE IORMPLAN to display a list of valid attributes.

CELL-02545: Invalid IORMPLAN latency value.

Cause: An invalid value was specified in a CellCLI command.

Action: Use DESCRIBE IORMPLAN to display a list of valid attributes.

CELL-02546: I/O Resource Manager (IORM) plan push: {0}

Cause: The IORMPLAN plan could not be pushed from CellCLI or Management Server to Cell Server.

Action: Contact Oracle Support Services.

CELL-02547: Cannot communicate with Cell Server (CELLSRV).

Cause: Management Server could not communicate with Cell Server. Cell Server may have failed.

Action: Restart Cell Server with the ALTER CELL command.

See Also:

ALTER CELL
CELL-02548: Grid disk is in use.

Cause: The grid disk was in use.

Action: Make the grid disk inactive, and then retry the command.

See Also:

DROP GRIDDISK
CELL-02549: Grid disk is in use and FORCE is not specified for the operation.

Cause: The grid disk was in use, and required the FORCE option to complete the operation was not specified.

Action: Enter the CellCLI command using the FORCE option.

CELL-02550: Cell Server (CELLSRV) cannot drop the grid disk.

Cause: Cell Server (CELLSRV) could not drop the grid disk due to an error.

Action: Restart CELLSRV with the ALTER CELL command. Then drop the grid disk.

See Also:

CELL-02551: Invalid command arguments.

Cause: Invalid or missing arguments raised an error with the CellCLI command.

Action: Check the help text for the valid command syntax.

See Also:

HELP
CELL-02556: Attribute value must be greater than zero: {0}

Cause: A value equal to or less than zero was entered for the attribute.

Action: Enter a numeric value greater than zero for the attribute.

CELL-02557: Attribute value must be positive: {0}

Cause: A value equal to or less than zero was entered for the attribute.

Action: Enter a numeric value greater than zero.

CELL-02558: UUID is NULL. Cannot drop from Cell Server (CELLSRV).

Cause: An internal error occurred.

Action: Contact Oracle Support Services.

CELL-02559: There is a communication error between MS and CELLSRV.

Cause: Management Server could not communicate with Cell Server.

Action: Restart Cell Server with the ALTER CELL command.

See Also:

ALTER CELL
CELL-02560: Duplicate name.

Cause: There was an existing object with the same name.

Action: Choose a unique name for the object for the cell.

CELL-02561: Cell disk already exists on the specified device.

Cause: There was a cell disk already on the device.

Action: Drop the existing cell disk before retrying the operation, or specify a different device for the new cell disk.

CELL-02563: Specified partition cannot be formatted.

Cause: An error occurred when trying to format the specified partition.

Action: Contact Oracle Support Services.

CELL-02564: Specified object does not exist.

Cause: An invalid object was specified with a command.

Action: Use LIST object_type to display a list of valid objects for the specified object type. Check the help text for the valid command syntax.

See Also:

CELL-02565: Wrong offset specified.

Cause: An incorrect offset value was entered.

Action: Re-enter the command with a valid offset value.

See Also:

CREATE GRIDDISK
CELL-02566: No space for the specified allocation.

Cause: No free space was available for the allocation specified.

Action: Contact Oracle Support Services.

CELL-02568: One or more grid disks exist on the specified cell disk.

Cause: Existing grid disks were found on the cell disk specified in the operation.

Action: Drop the existing grid disks before retrying the operation on the specified cell disk or specify a different cell disk for the operation.

CELL-02569: Invalid grid disk state.

Cause: A problem occurred with the state of the grid disk.

Action: Contact Oracle Support Services.

CELL-02574: Invalid message sent by management command.

Cause: An invalid message was sent by Management Server.

Action: Contact Oracle Support Services.

CELL-02575: The value for notificationPolicy should be NONE or any combination of CRITICAL, WARNING, and CLEAR.

Cause: The valid value for notificationPolicy was not none or a combination of critical, warning, or clear.

Action: Enter one of the valid combinations displayed in the error message.

See Also:

ALTER CELL
CELL-02576: The value for notificationMethod should be MAIL, SNMP, both MAIL and SNMP, or NONE.

Cause: The valid value for notificationMethod was not mail, snmp, a combination of the two values, or none.

Action: Enter one of the valid options displayed in the error message.

See Also:

ALTER CELL
CELL-02577: CREATE GRIDDISK ALL and DROP GRIDDISK ALL commands require a prefix attribute.

Cause: When the CREATE GRIDDISK and DROP GRIDDISK commands are run with the ALL option, the prefix attribute must be specified to indicate the prefix of the disk names.

Action: Check the Help text for the valid command syntax, and the syntax of a specific command.

CELL-02578: An error was detected in the SMTP configuration: {0}.

Cause: A problem occurred with the SMTP configuration for the cell.

Action: Use ALTER CELL to correct the SMTP configuration.

See Also:

ALTER CELL
CELL-02579: An error was detected in the SNMP configuration: {0}.

Cause: A problem occurred with the SNMP configuration for the cell.

Action: Use ALTER CELL to correct the SNMP configuration.

See Also:

ALTER CELL
CELL-02580: An error occurred while retrieving metrics: {0}.

Cause: A problem occurred when retrieving metrics for the cell.

Action: Contact Oracle Support Services.

CELL-02581: Cell disk {0} on LUN {1} has not been exported and FORCE is not specified for import.

Cause: The cell disk had not been properly exported with the EXPORT command on a cell before the cell disk was moved to a different cell. This problem can occur if EXPORT had not been run on the cell disk.

Action: Use the FORCE option when running the IMPORT command on the cell disk.

CELL-02582: The structures for the cell disk on LUN {0} cannot be erased from CELLSRV memory.

Cause: A problem occurred while attempting an EXPORT or IMPORT operation.

Action: Contact Oracle Support Services.

CELL-02583: The operation is not permitted on this cell disk.

Cause: A problem occurred while attempting an EXPORT or IMPORT operation. For example, a grid disk cannot be created on a cell disk that was in a Requires Import state.

Action: Contact Oracle Support Services.

CELL-02590: Preexisting threshold: {0}.

Cause: The threshold names were already used.

Action: Use a unique threshold name.

CELL-02591: Threshold does not exist: {0}.

Cause: The threshold name did not exist.

Action: Use an existing threshold name.

See Also:

ALTER THRESHOLD
CELL-02592: Threshold comparison operator must be '<', '<=', '=', '>=', or '>'.

Cause: An incorrect comparison operator was entered.

Action: Use '<', '<=', '=', '>=', or '>' for the comparison operator.

CELL-02593: Threshold name must identify a valid metric: {0}.

Cause: An invalid metric name was entered.

Action: Use an existing metric name.

CELL-02594: Threshold comparison attribute required.

Cause: A comparison operator was not entered with this specified metric.

Action: Enter a comparison operator when creating a threshold for this metric.

CELL-02595: Thresholds are not supported for this metric: {0}.

Cause: A threshold was created on a metric that was not supported.

Action: Create a threshold for a supported metric.

CELL-02596: The IPaddress attribute {0} is not in correct CIDR format.

Cause: The ipaddress attribute was incorrect.

Action: Enter a valid IP address format.

See Also:

CREATE CELL
CELL-02597: Could not update the network configuration file: {0}.

Cause: The network configuration was not updated.

Action: Contact Oracle Support Services.

CELL-02598: Ipaddress/Netmask attribute is not properly configured for interconnect {0}.

Cause: The ipaddress attribute was not valid for the corresponding interconnect attribute.

Action: Enter a valid IP address.

See Also:

CREATE CELL
CELL-02599: Cannot determine HostName. Please specify cellname.

Cause: The host name of the cell was not identified.

Action: Enter a name for the cell.

See Also:

CREATE CELL
CELL-02600: Interconnect1 must be specified if interconnect2 is specified.

Cause: The interconnect2 attribute was specified, but interconnect1 was not.

Action: Specify interconnect1 before specifying interconnect2.

See Also:

CREATE CELL
CELL-02601: Interconnect2 must be specified if interconnect3 is specified.

Cause: The interconnect3 attribute was specified, but interconnect2 was not.

Action: Specify interconnect2 before specifying interconnect3.

See Also:

CREATE CELL
CELL-02602: Interconnect3 must be specified if interconnect4 is specified.

Cause: The interconnect4 attribute was specified, but interconnect3 was not.

Action: Specify interconnect3 before specifying interconnect4.

See Also:

CREATE CELL
CELL-02607: Specify at least one network interconnect.

Cause: A network interconnection was not specified.

Action: Specify at least the interconnect1 attribute.

See Also:

CREATE CELL
CELL-02608: A valid network interconnect is not specified.

Cause: A valid network interconnection was not specified.

Action: Specify a valid network interconnection.

See Also:

CELL-02610: An invalid setting was specified for the traceLevel attribute. Specify a valid JAVA logging level (SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST), or a valid ODL logging level (INCIDENT_ERROR:1, ERROR:1, WARNING:1, NOTIFICATION:1, NOTIFICATION:16, TRACE:1, TRACE:16, TRACE:32).

Cause: An invalid setting was specified for the traceLevel attribute with the ALTER CELL command.

Action: Specify a valid JAVA logging level or a valid ODL logging level for the traceLevel attribute.

CELL-02611: Cannot access the specified device.

Cause: A device was not accessible.

Action: Contact Oracle Support Services.

CELL-02612: Operation cannot be completed due to IO errors.

Cause: An operation failed because of I/O errors.

Action: Contact Oracle Support Services.

CELL-02613: Operation failed because the cell disk is corrupted.

Cause: A cell disk was corrupted.

Action: Contact Oracle Support Services.

CELL-02614: The role attribute value must be PRIMARY or STANDBY.

Cause: The role attribute was not specified correctly.

Action: Specify the role attribute as primary or standby.

See Also:

ALTER IORMPLAN
CELL-02615: The role attribute is not permitted on catplan directives.

Cause: The role attribute was specified for a catPlan directive.

Action: Remove the role attribute from the catPlan directive.

See Also:

ALTER IORMPLAN
CELL-02616: The role attribute is not permitted on dbplan 'other' directives.

Cause: The role attribute was specified for the dbPlan other directive.

Action: Remove the role attribute from the dbPlan other directive.

See Also:

ALTER IORMPLAN
CELL-02617: A name list is permitted only for dbplan directives with 'role=primary'.

Cause: A name list was specified for dbPlan directives that did not have role equal to primary.

Action: Remove the role attribute from the dbPlan directive.

See Also:

ALTER IORMPLAN
CELL-02618: Current IORMPLAN state is not 'inactive'.

Cause: The IORMPLAN state was not inactive.

Action: Change the IORMPLAN state to inactive.

See Also:

ALTER IORMPLAN
CELL-02619: Current IORMPLAN state is not 'active'.

Cause: The IORMPLAN state was not active.

Action: Change the IORMPLAN state to active.

See Also:

ALTER IORMPLAN
CELL-02620: An unmapped CELLSRV error has occurred. The internal message is: {0}.

Cause: An unexpected error was returned to Management Server from Cell Server.

Action: Contact Oracle Support Services.

CELL-02621: Interface {0} is neither Ethernet nor InfiniBand.

Cause: An invalid interface was entered.

Action: Enter a valid Ethernet or InfiniBand interface.

CELL-02622: Interface {0} supports bootproto {1}. It must be either static or dhcp.

Cause: An invalid interface was entered.

Action: Enter static or dhcp.

CELL-02623: The command “{0}” returned an error code {1}.

Cause: An error occurred while running the command.

Action: Contact Oracle Support Services.

CELL-02624: Error while executing command {0}.

Cause: An error occurred while running the command.

Action: Contact Oracle Support Services.

CELL-02625: Interface {0} refers to device name {1}. Device name must be same as Interface name.

Cause: The network configuration was not consistent between the interface and device name.

Action: Contact Oracle Support Services.

CELL-02626: Interface {0} configuration file {1} not found.

Cause: Network configuration file was not found.

Action: Contact Oracle Support Services.

CELL-02627: There is a communication error between MS and CELLSRV. Configuration file cellinit.ora is malformed or does not include required information.

Cause: The cellinit.ora file did not have the correct information or the correct format.

Action: Edit the cellinit.ora file to correct the problem.

CELL-02628: There is an internal error in the MS-CELLSRV communication module. Create an incident package and submit the package to Oracle Support Services.

Cause: An error occurred in the MS-CELLSRV communication module.

Action: Create an incident package and submit the package to Oracle Support Services.

CELL-02629: Client does not have required privileges to perform this operation.

Cause: The operation did not have the required privileges, and was refused by CELLSRV.

Action: Contact Oracle Support Services.

CELL-02630: There is a communication error between Management Server and Cell Server caused by a mismatch of security keys. Check that both servers have access to and use the same $OSSCONF/cellmskey.ora file.

Cause: The security keys for Management Server and Cell Server did not match.

Action: Contact Oracle Support Services.

CELL-02632: Operation failed because the disk GUID is not unique.

Cause: Two cell disks have identical identifiers (GUID). The most likely cause is that a cell disk was duplicated by copying its content of underlying LUN or partition to another disk using OS utilities.

Action: Make underlying LUN or partition with duplicated content unavailable to the operating system, such as by removing the physical disk from the system.

CELL-02633: Disk in use.

Cause: The requested operation was denied because the disk is currently busy.

Action: Retry the operation later.

CELL-02634: Disk is currently erasing data.

Cause: The requested operation was denied because the disk is currently erasing data.

Action: Retry the operation after the erase procedure completes.

CELL-02635: One or more grid disks on the cell disk are currently erasing data.

Cause: The requested operation was denied because the grid disks are currently erasing data.

Action: Retry the operation after the erase procedure completes.

CELL-02636: Cannot alter or drop built-in thresholds.

Cause: The DROP or ALTER command specified a built-in threshold. Built-in thresholds cannot be dropped or altered.

Action: Retry the command without specifying a built-in threshold.

CELL-02637: Response returned by cellsrv is invalid.

Cause: The CELLSRV response to the CellCLI command was invalid.

Action: Contact Oracle Support Services.

CELL-02638: Name list is not supported for dbplan directives.

Cause: A name list was specified in the database plan.

Action: Specify the plan without the name list, and specify the databases as separate directives.

CELL-02639: The IPaddress and IPblock attributes are no longer supported. Use the interconnect attribute instead.

Cause: The IPaddress or IPblock attributes were specified as part of the CREATE CELL command.

Action: Retry the command and specify only the interconnect attributes.

CELL-02640: Interconnect{0} cannot be removed because interconnect{1} has been previously specified, or is specified in the current command.

Cause: The user was attempting to remove an IP address that is between two other IP addresses, such as removing ipaddress2 when ipaddress1 and ipaddress3 are in use.

Action: Remove interconnectN+1 before removing interconnectN.

CELL-02641: Interconnect{1} must be specified if interconnect{0} is specified.

Cause: The user was attempting to specify interconnectN+1 before specifying interconnectN.

Action: Specify the interconnections in order. Multiple interconnections can be specified in the same command.

CELL-02642: An empty string cannot be specified for an IP address with the non-empty interconnect{0}. Do not specify an IP address if it should be read from the network. Specify empty strings for both the IP address and interconnect, or specify only one as empty if you want the interconnect deleted.

Cause: An IP address was specified for a non-empty interconnection.

Action: The user must specify either one, or both, as empty. For example: ALTER CELL interconnect1="", ALTER CELL ipaddress1="", or ALTER CELL interconnect1="", ipaddress1="".

CELL-02643: DROP ALERTHISTORY command did not include all members of the alert sequence for {0}. All members of the sequence must be dropped together.

Cause: The command did not include all members of the alert sequence.

Action: The user must include all members in the alert sequence when dropping stateful alerts.

CELL-02644: Flash cache does not exist.

Cause: The DROP FLASHCACHE or ALTER FLASHCACHE command failed because flash cache does not exist.

Action: Do nothing, or use the CREATE FLASHCACHE command to create the flash cache.

CELL-02645: Flash cache already exists.

Cause: The CREATE FLASHCACHE command failed because flash cache already exists.

Action: Do nothing, or use the ALTER FLASHCACHE command to change the existing flash cache.

CELL-02646: CREATE GRIDDISK failed due to insufficient free space on cell disks: {0}.

Cause: The CREATE GRIDDISK command failed because there was insufficient free space on the cells based on the size attributed specified in the command.

Action: Do nothing. The grid disks are created on other cell disks.

CELL-02647: Flashcache requires Flash cell disks. The cell disk provided is not a working Flash cell disk: <cd-name>.

Cause: The CREATE FLASHCACHE CELLDISK command failed because a flash cell disk was not specified.

Action: Specify a flash cell disk when creating Exadata Smart Flash Cache.

CELL-02648: Cannot export cell disk that has Smart Flash Cache on it: {0}.

Cause: The cell disk cannot be exported because the cell disk was defined on Exadata Smart Flash Cache.

Action: Correct the command to export a different cell disk.

CELL-02649 Cannot get Flash Cache information from Cell Server (CELLSRV).

Cause: An internal error occurred.

Action: Contact Oracle Support Services.

CELL-02650: An invalid setting {0} was specified for the collectionLevel attribute. Specify a valid collection level.

Cause: An invalid collection level was specified in the command.

Action: Specify a valid collection level.

CELL-02651: There is a communication error between MS and CELLSRV caused by an unrecognized configuration file version.

Cause: An internal error occurred.

Action: Contact Oracle Support Services.

CELL-02652: CREATE FLASHCACHE failed due to insufficient free space on cell disks: {0}

Cause: There was not enough free space on the cell.

Action: Do nothing. The flash cache are created on other cell disks.

CELL-02660: Invalid value for attribute: {0}.

Cause: The ALTER command that was entered had an incorrect value in its assignment to an attribute.

Action: Fix the ALTER command to use the correct value format.

CELL-02661: The grid disk resize operation has failed for {0}.

Cause: An invalid size was requested for the grid disk, and there is not sufficient space available on the cell disk.

Action: Use LIST GRIDDISK DETAIL to determine the current size of the grid disk, and LIST CELLDISK DETAIL to determine the available free space on the cell disk.

CELL-02662: This operation is denied because a resize operation is currently running for grid disk {0}.

Cause: A resize operation was already in progress on the grid disk. Only one resize is allowed.

Action: Use LIST GRIDDISK grid_disk ATTRIBUTES lastResizeStatus to monitor the resize status of grid_disk before issuing a new resize request.

CELL-02663: Resize operation is currently running on one of the grid disks of the cell disk.

Cause: A resize operation was already in progress on another grid disk of the same cell disk.

Action: Use LIST GRIDDISK to find all the grid disks of the cell disk. Next, use LIST GRIDDISK grid_disk ATTRIBUTES lastResizeStatus to determine if any of the grid disks are still being resized before issuing a new resize request.

CELL-02664: Failed to create FLASHCACHE on cell disk {0}. Received error: {1}.

Cause: CELLSRV was unable to create flash cache.

Action: Correct the problem indicated by the attached error, if possible. If that does not correct the problem, then contact Oracle Support Services.

CELL-02665: FLASHCACHE exists on the specified cell disk.

Cause: Flash cache was not created because it already exists on the cell disk.

Action: Contact Oracle Support Services.

CELL-02667: An SNMP subscription of type ASR is required in the snmpSubscriber attribute.

Cause: A valid ASR SNMP command was run, but ASR subscription was not set up.

Action: Set the SNMP subscriber cell attributes using the ALTER CELL command.

See Also:

ALTER CELL
CELL-02668: An error occurred during ASR SNMP setup for ILOM: {0}

Cause: The ASR subscription setup for the ILOM failed for the reason shown in the message.

Action: Correct the problem described in the message. If that does not correct the problem, then contact Oracle Support Services.

CELL-02669: No slots are available for ILOM SNMP subscribers.

Cause: The ASR subscription setup failed due to lack of slots in the ILOM table.

Action: Remove any unneeded entries in the ILOM table, if possible. If that is not possible, then contact Oracle Support Services.

CELL-02670: Hostname could not be resolved for ILOM SNMP setup.

Cause: A DNS or other network configuration error prevented the ASR host from being contacted.

Action: Correct the network configuration error, if possible. If that does not correct the problem, then contact Oracle Support Services.

CELL-02672: An ILOM error occurred during ASR setup. A retry of this command may be successful.

Cause: The ILOM was busy.

Action: Retry the command. If that does not correct the problem, then contact Oracle Support Services.

CELL-02673: Invalid value of time for bbuLearnCycleTime: {0}

Cause: The value specified for the battery backup learn cycle was not valid.

Action: Specify the learn cycle time in a valid date time format, such as 2012-01-02T08:58:38-08:00.

CELL-02674: Cannot get top cpu information from Cell Server (CELLSRV).

Cause: MS was unable to retrieve the top CPU information from CELLSRV.

Action: This retrieval process is performed by Oracle Enterprise Manager, and is automatically retried at a later time.

CELL-02675: Cannot get quarantine information from Cell Server (CELLSRV).

Cause: A communication error prevents retrieval of quarantine information from CELLSRV.

Action: Check that CELLSRV is running, and start it if it is not running. Otherwise, contact Oracle Support Services.

CELL-02676: Quarantine does not exist: {0}.

Cause: The quarantine identifier specified on the CellCLI command does not match an existing quarantine.

Action: Use the LIST QUARANTINE command to list the available quarantine entries. Use the name of an available quarantine.

CELL-02677: Cannot drop the quarantine. Error: {0}.

Cause: The quarantine could not be dropped due to an error

Action: Correct the specified error before attempting to drop the quarantine again.

CELL-02678: Cannot alter the quarantine. Error: {0}.

Cause: The quarantine could not be altered due to an error.

Action: Correct the specified error before attempting to alter the quarantine again.

CELL-02679: Cannot add the quarantine. Error: {0}.

Cause: The quarantine could not be created due to an error.

Action: Correct the specified error before attempting to create the quarantine again.

CELL-02680: Quarantine creation requires that attribute {0} be assigned one of the following values: {1}.

Cause: The quarantine type attribute was not provided or it was not assigned a correct type value.

Action: Correct the CREATE QUARANTINE command to contain a valid quarantineType.

CELL-02681: IORMPlan objective requires one of the following values: {0}.

Cause: The ALTER IORMPLAN command specified an incorrect object value.

Action: Enter the command with a correct value.

See Also:

ALTER IORMPLAN
CELL-02682: Invalid Quarantine ID.

Cause: The quarantine operation used an invalid quarantine identifier.

Action: Contact Oracle Support Services.

CELL-02683: Quarantine Manager Disabled.

Cause: The fault isolation feature has been disabled.

Action: Contact Oracle Support Services.

CELL-02684: Quarantine Manager Unknown Error.

Cause: Action failed due to an unknown error.

Action: Contact Oracle Support Services.

CELL-02685: Invalid Attribute for the Quarantine Type Specified.

Cause: A CREATE QUARANTINE or ALTER QUARANTINE command specified invalid attributes.

Action: Correct the attributes, and reissue the command.

CELL-02686: Duplicate Quarantine Entry.

Cause: A CREATE QUARANTINE command attempted to create a quarantine that already exists.

Action: If a different quarantine was intended, then modify the attributes to specify the new quarantine.

CELL-02696: The following attributes of IBPort {0} are undefined: {1}

Cause: The reset of the InfiniBand counters failed because the logical identifier or port number was not defined.

Action: Contact Oracle Support Services.

CELL-02697: Invalid ERASE option specified. Please use one of the following '1pass', '3pass', or '7pass'.

Cause: The DROP CELLDISK ERASE or DROP GRIDDISK ERASE command specified an incorrect erase option.

Action: Retry the command using valid options. If that does not correct the problem, then contact Oracle Support Services.

CELL-02698: Secure data deletion for {0} failed. Please check physical LUN status.

Cause: The DROP CELLDISK ERASE or DROP GRIDDISK ERASE command failed due to a bad LUN status.

Action: Check the status of the LUN associated with the cell disk or grid disk, and retry the command. If that does not correct the problem, then contact Oracle Support Services.

CELL-02699: Terminating LIST output: MS timed out waiting for CellCLI. A retry of this LIST command may be successful.

Cause: MS reached the time limit waiting for CellCLI to list output.

Action: CellCLI may be stalled for a reason under user control. Restart CellCLI, and retry the command.

CELL-02711: The share attribute is not permitted with catplan directives.

Cause: The catPlan directives included the share attribute.

Action: Remove the share attribute from the catPlan.

See Also:

ALTER IORMPLAN
CELL-02712: The flashCacheLimit attribute is not permitted with catplan directives.

Cause: The flashcachelimit attribute was specified with the catPlan directives.

Action: Remove the flashcachelimit attribute from the catPlan directive.

CELL-02713: The flashCacheMin attribute is not permitted with catplan directives.

Cause: The flashcacheminattribute was specified with the catPlan directives.

Action: Remove the flashcachemin attributed from the catPlan directive.

CELL-02714: The flashcache attribute cannot be set to OFF if flashCacheLimit, flashCacheSize, or flashCacheMin is specified.

Cause: The flash cache attribute was set to OFF when the flashcachelimit, flashcachesize or flashcachemin attributes were specified.

Action: Set the flash cache attribute to ON when using the flashcachelimit, flashcachesize or flashcachemin attributes.

CELL-02715: The flashCacheLimit value cannot be zero.

Cause: The flashcachelimit attribute was set to zero.

Action: Set the flashcachelimit to a value other than zero.

CELL-02716: The {0} attribute is not permitted with profile plans.

Cause: The attribute was specified for a profile plan.

Action: Profile directives do not support certain attributes. Use valid attributes with database type directives to specify resources for a database in primary or standby mode.

CELL-02717: The type attribute is not permitted with catplan directives.

Cause: The type attribute was specified for a catPlan parameter.

Action: The type attribute is not supported in catPlan parameters. Remove the type attribute from the category plan.

CELL-02718: Setting IORMPLAN type to profile is not permitted with dbplan {0} directive.

Cause: The profile type was included in a dbPlan directive that also had the specified directive.

Action: Certain directives do not support certain attributes. Remove type=profile from the DEFAULT and OTHER directives.

CELL-02719: The flashCacheLimit value cannot be greater than the current flashcache size: {0}.

Cause: The flashcachelimit value was greater than the current flash cache size.

Action: Re-enter the command with a lower value for the flashcachelimit attribute.

CELL-02720: The flashCacheLimit value cannot be less than the flashCacheMin value.

Cause: The flashcachelimit value was less than the flashcachemin value.

Action: Re-enter the command with a higher value for the flashcachelimit attribute.

CELL-02721: Flash log does not exist.

Cause: The command required the existence of flash log, and flash log did not exist.

Action: Create the flash log, and then retry the command.

CELL-02722: Flash log already exists.

Cause: The CREATE FLASHLOG command did not succeed because flash log already exists.

Action: Remove the flash log using the DROP FLASHLOG command, and then retry the CREATE FLASHLOG command.

CELL-02723: CREATE FLASHLOG failed due to insufficient free space on cell disks: {0}.

Cause: The flash log was not created due to insufficient space on the cell disks.

Action: Create space on the flash cell disks by dropping the grid disks or dropping the flash cache, and then recreate it with a smaller size.

CELL-02724: Flashlog requires Flash cell disks. The cell disk provided is not a working Flash cell disk: {0}.

Cause: Flash log was not created because the cell disk was not a flash cell disk.

Action: Create the flash log on a flash disk.

CELL-02725: Cannot export cell disk that has Smart Flash Log on it: {0}.

Cause: Cell disk was not exported because it contains Smart Flash Log.

Action: Use the DROP FLASHLOG command to remove flash log from the disk, and then retry the EXPORT command.

CELL-02726: Cannot get Flash Log information from Cell Server (CELLSRV).

Cause: MS was unable to retrieve the flash log information from CELLSRV.

Action: If CELLSRV is not running, then start CELLSRV using the ALTER CELL STARTUP SERVICES command. If the problem persists while CELLSRV is running, then contact Oracle Support Services.

CELL-02727: Failed to create FLASHLOG on cell disk {0}. Received error: {1}.

Cause: Flash log was not created on the cell disk.

Action: Correct the problem indicated by the error message, if possible, and then retry the CREATE FLASHLOG command.

CELL-02728: FLASHLOG exists on the specified cell disk.

Cause: Flash log already existed on the cell disk.

Action: Contact Oracle Support Services.

CELL-02729: Invalid ERASE option for {0} specified. Please use '7pass' for flashdisk.

Cause: An invalid ERASE option was used for the flash disk.

Action: Enter the correct ERASE option for the DROP CELL command.

CELL-02730: Specified cell disk is not FLASH: {0}. Use ALTER CELLDISK to flush all dirty pages TO a hard cell disk.

Cause: The ALTER FLASHCACHE FLUSH command specified a hard cell disk, not flash cell disk. The command can only be used to flush pages from a flash cell disk.

Action: Use the ALTER CELLDISK FLUSH command to flush the dirty pages to a hard cell disk.

CELL-02731: Specified cell disk is FLASH: {0}. Use ALTER FLASHCACHE to flush all dirty pages FROM a flash cell disk.

Cause: The ALTER CELLDISK FLUSH command specified a flash cell disk, not hard cell disk. The command can only be used to flush pages to a hard cell disk.

Action: Use the ALTER FLASHCACHE FLUSH to flush all dirty pages from the flash cell disk.

CELL-02732: There may be data not synchronized to the grid disks (dirty data) in flash cache. Use ALTER FLASHCACHE to flush the dirty data and to stop caching, and then retry the command.

Cause: The data is not synchronized in the flash cache.

Action: Use the ALTER FLASHCACHE command to flush the dirty data from the flash disks to the grid disks, and then retry the command.

CELL-02740: IORM directive contains repeated attributes: {0}. Only a single occurrence of an attribute is allowed in each directive.

Cause: An IORM directive included repeated attributes.

Action: Correct the IORM directive using the ALTER IORMPLAN command.

CELL-02741: IORM directives contain multiple assignments of attribute “{0}” for database “{1}”. Only a single assignment of this attribute is allowed for each database.

Cause: An IORM directive included multiple assignments of an attribute.

Action: Correct the IORM directive using the ALTER IORMPLAN command.

CELL-02742: The Flashlog size must not require more than 4G on each flash celldisk.

Cause: The flash log size entered was greater than 4 GB for each flash cell disk.

Action: Set the flash log size to be less than 4 GB for each flash cell disk.

CELL-02743: Invalid value for "cachingPolicy" attribute: "{0}". Must be "none" or "default."

Cause: An invalid value was entered for the caching attribute.

Action: Enter a valid value for the attribute. Valid values are none or default.

CELL-02744: Cannot specify cachingPolicy of "none" for flash griddisks.

Cause: The attribute value was specified as none for the flash grid disks.

Action: Enter a valid value for the attribute.

CELL-02745: Flashcache is not in the correct status to perform flush operation.

Cause: The status for flash cache was incorrect, and the flush operation did not succeed.

Action: Correct the status, and run the command again.

CELL-02746: Flashcache flush failed.

Cause: The flush operation failed.

Action: If the operation failed because of a temporary outage of the flash disk or the cached Grid Disk, then try the FLUSH command after the disk is reinstated.

CELL-02750: IORM directives contain multiple assignments of attribute “{0}” for profile “{1}”. Only a single assignment of this attribute is allowed for each profile.

Cause: The IORM directives contained multiple assignments for the attribute.

Action: Remove the multiple assignments for the attribute, and then specify only one attribute assignment.

CELL-02767: Flash cache operation timed out.

Cause: CELLSRV failed to complete the flash cache operation within the expected interval.

Action: Contact Oracle Support Services.

CELL-02768: Flash cache initialization is not complete.

Cause: Flash cache initialization was not yet complete.

Action: Retry the command after a few seconds. If the problem continues, then contact Oracle Support Services.

CELL-02769: Cannot complete flash cache drop on: {0}. Received error: {1} Flash cache was not dropped on these cell disks: {2}.

Cause: The flash cache DROP operation did not complete successfully.

Action: The error occurred while dropping the specified disk. The listed disks are still active in flash cache.

CELL-02770: Cannot begin flushing flash cache on: {0}. Received error: {1} Flash cache flush was not started on these cell disks: {2}.

Cause: The flash cache on the specified cell disks was not flushed due to an error.

Action: If the failure occurred because of a temporary disk outage, then the FLUSH command can be retried after the disks are back online. If the failure was not caused because of a temporary disk outage, then contact Oracle Support Services.

CELL-02771: Cannot cancel flash cache flush on: {0}. Received error: {1} Flash cache flush was not canceled on these cell disks: {2}.

Cause: The CANCEL FLUSH command failed with an error.

Action: Contact Oracle Support Services.

CELL-02772: Cannot create or alter flash cache due to unequal cell disk sizes

Cause: The flash cache could not be created or altered because the cell disk sizes are not the same.

Action: Contact Oracle Support Services.

CELL-02775: FlashCacheMode value {0} is invalid. Value must be set to {1} or {2}.

Cause: The value entered in the command was invalid.

Action: Enter a correct value. Values are writethrough or writeback.

CELL-02776: Flash cache must be dropped before changing flashCacheMode to {0}.

Cause: Flash cache was not dropped before running the ALTER CELL command.

Action: Drop flash cache, and run the command again.

CELL-02777: Flash cache mode {0} is already in effect.

Cause: The mode entered in the command was already in effect.

Action: Check the command, and change the mode, if it is necessary to complete the command.

CELL-02778: Flash cache is not in write back mode.

Cause: The command entered is only valid in writeback mode.

Action: Check the command, and change to write-back mode, if necessary to complete the command.

CELL-02779: At least one of the following attributes needs to be specified: {0}.

Cause: The interdatabase plan or the category database plan was not specified when setting an interdatabase IORM quarantine.

Action: Specify the interdatabase plan or the category database plan when creating the quarantine.

CELL-02780: IORM Plan is quarantined and cannot be set.

Cause: The IORM plan was quarantined, and cannot be set.

Action: Delete the IORM plan quarantine before setting the IORM plan.

CELL-02782: FLASHCACHE and FLASHLOG parts exist on the specified cell disk.

Cause: Flash cache and flash log existed on the cell disk.

Action:

CELL-02783: CREATE FLASHCACHE requires at least one working flash cell disk.

Cause: No working flash cell disk was found.

Action: Repair the flash disks listed in the command, or change the command to specify working cell disks, and then reissue the command.

CELL-02784: Operation failed because the disk is not a cell disk.

Cause: The operation failed because the disk was not a cell disk.

Action: If the data on the disk is not needed, then either replace the disk with another disk or overwrite the cell disk using the CREATE CELLDISK FORCE command. If the data is needed, then contact Oracle Support Services.

CELL-02785: Operation failed because the cell disk version is from an incompatible release.

Cause: The cell disk metadata was not supported.

Action: The cell disk has a later release. If the data on the disk is not needed, then either replace the disk with another disk or overwrite the cell disk using the CREATE CELLDISK FORCE command. If the data is needed, then contact Oracle Support Services.

CELL-02789: Invalid format for bbuLearnSchedule: “{0}”. Command syntax is “[MONTH number][[DATE number]|[[WEEK number][DAY number]]][HOUR number]”

Cause: An incorrect format was used when setting the battery backup learn cycle.

Action: Correct the format, and then run the command.

See Also:

ALTER CELL
CELL-02790: LearnSchedule field “{0}” is invalid. It should be one of MONTH, DAY, WEEK, DATE, HOUR, MINUTE, SECOND.

Cause: An incorrect attribute was specified when setting the battery backup learn cycle

Action: Correct the attribute, and then run the command.

See Also:

ALTER CELL
CELL-02791: LearnSchedule field: {0} value {1} is invalid. It should be between {2} and {3}.

Cause: An incorrect value was specified for the attribute.

Action: Correct the value, and then run the command.

See Also:

ALTER CELL
CELL-02792: DATE can not be specified with WEEK/DAY.

Cause: A date value was entered with a WEEK or DAY parameter.

Action: Correct the value, and then run the command.

CELL-02793: Cannot add the offload group. Error: {0}.

Cause: There was an error when adding an offload group.

Action: Correct the issue, and retry the command.

CELL-02822: CREATE CELL RESCUE command cannot accept FLASHCACHE or FLASHLOG size.

Cause: The size for the flash cache or flash log was included in the command.

Action: Re-enter the command without specifying the size.

CELL-02827: Configuration check for hardware and firmware encountered the following issues: {0}.

Cause: The configuration check encountered an error.

Action: Correct the issue, and retry the command.

CELL-02828: The BBU DROP FOR REPLACEMENT command is only supported on Exadata X3-n and X4-n.

Cause: The BBU DROP FOR REPLACEMENT command was run on Oracle Exadata Database Machine models earlier than X3-n.

Action: Run the command on hardware that is X3-n or later.

CELL-02829: The BBU REENABLE command is only supported on Exadata X3-n and X4-n.

Cause: The BBU REENABLE command was run on Oracle Exadata Database Machine models earlier than X3-n.

Action: Run the command on hardware that is X3-n or later.

CELL-02830: The BBU DROP FOR REPLACEMENT command cannot drop HDD disk controller battery because the battery is not present.

Cause: The BBU DROP FOR REPLACEMENT command was run but the battery was not present.

Action: This message is informational. No action is needed.

CELL-02831: The BBU REENABLE command cannot re-enable HDD disk controller battery because the battery was not dropped using the BBU DROP FOR REPLACEMENT command.

Cause: The BBU REENABLE command was run, but the battery was not dropped.

Action: Drop the battery using the BBU DROP FOR REPLACEMENT command, and then run the BBU REENABLE command.

CELL-02832: An error occurred while setting the LUN cache mode to writeThrough.

Cause: An error occurred while setting the LUN cache mode to writeThrough mode.

Action: Re-run the BBU DROP FOR REPLACEMENT command.

CELL-02833: An error occurred while setting the LUN cache mode to writeBack.

Cause: An error occurred while setting the LUN cache mode to writeBack mode.

Action: Re-run the BBU ENABLE command.

CELL-02834: HDD disk controller battery was already been dropped.

Cause: The BBU DROP FOR REPLACEMENT command was run, but the battery was already dropped.

Action: This message is informational. No action is needed.

CELL-02835: The operation may cause disk groups to dismount due to reduced redundancy. To continue and discard data on the specified disks, shut down Oracle ASM and then retry the command.

Cause: The disk group could not be dropped because dropping it would cause a reduction in redundancy.

Action: Discard the data on the specified disks, shut down the Oracle ASM instance, and then drop the disk group.

CELL-02836: Loss of data on griddisks using flash cache may occur due to reduced redundancy. Use ALTER FLASHCACHE to flush data from flash cache, and then retry the command.

Cause: The command failed because the flash cache is in writeBack mode and caching data for disks with reduced redundancy.

Action: Use the ALTER FLASHCACHE command to flush data from the flash cache, and then retry the command.

CELL-02837: Cannot begin flushing flash cache. Cell disk {0} is not a part of the flash cache.

Cause: The flash cache was not flushed because the specified cell disk is not part of the flash cache.

Action: Enter the command without specifying the disk names.

CELL-02838: CREATE FLASHLOG requires at least one working flash cell disk.

Cause: A working flash cell disk was not available.

Action: Check the alert history to determine why the flash disks are not normal. After the flash disks are repaired, retry the CREATE FLASHLOG command.

CELL-02839: Flash cache compression is not supported.

Cause: Flash cache compression was not supported for the flash card.

Action: Retry the command specifying the correct flash card.

CELL-02840: Invalid email alert interval. Use daily, weekly, biweekly or none.

Cause: An invalid value was entered for the e-mail alert interval.

Action: Enter the command using a valid interval. The valid values are daily, weekly, biweekly or none.

CELL-02842: Invalid hardDiskScrubInterval. Use daily, weekly, biweekly or none.

Cause: An invalid value was specified for the hardDiskScrubInterval.

Action: Enter the command using a valid interval. The valid values are daily, weekly, biweekly or none.

CELL-02843: Invalid date/time format for hardDiskScrubStartTime. Enter a valid format, such as {0}, or now.

Cause: An invalid value was specified for the hardDiskScrubStartTime value.

Action: Enter the command using a valid value. Valid values are date/time or now.

CELL-02844: Drop all flash cell disks before flash cache compression can be configured

Cause: Flash cache compression was not configured because the flash cell disks were not dropped.

Action: Drop the flash cell disks, and the retry the command.

CELL-02845: When flash cache compression is enabled, the total size of grid disks and flash log cannot exceed the physical size of the flash disk.

Cause:

Action:

CELL-02846: Flash compression configuration on this disk is different from that on the cell.

Cause:

Action:

CELL-02847: Failed to configure flash compression setting on the flash disks at PCI slots: {0}.

Cause:

Action:

CELL-02848: Failed to reclaim the free d space on flash disk.

Cause:

Action:

CELL-02849: Operation was interrupted.

Cause: MS shut down during a long-running operation.

Action: Restart MS to complete the operation.

CELL-02850: ERASE option is not supported on flash disks when flash cache compression is enabled.

Cause: The ERASE option was specified for flash disks that have flash cache compression enabled.

Action: The ERASE option is not supported with flash cache compression.

See Also:

ALTER CELL
CELL-02853: Cannot drop flash cache on cell disk {0}. There may be data that is not synchronized to the grid disks (dirty data) in flash cache. Use ALTER FLASHCACHE to flush the dirty data, stop caching, and then retry the DROP CELLDISK command.

Cause:The flash cache on the cell disk could not be dropped because of potentially unsaved data.

Action: Use the ALTER FLASHCACHE command to flush the dirty disk, and then retry the DROP CELLDISK command.

CELL-02857: Invalid ALTER FLASHCACHE value specified in the command. Flash cache size {0} cannot be downsized to {1}.

Cause:An invalid value was specified in the ALTER FLASHCACHE command.

Action: Enter the command using a smaller value.

CELL-02858: The ALTER FLASHCACHE command cannot proceed. The amount of free space {0} is less than the flash cache adjusted resize of {1}.

Cause: There was not enough free space to complete the command.

Action: Enter the command using a smaller value.

CELL-02859: The flash cache cannot be downsized. The minimum size flash cache can be set to is {0}. Reissue command with a size larger than the minimum size.

Cause: The value in the command was smaller than the minimum size allowed for flash cache.

Action: Enter the command using a valid value.

CELL-02860: The ALTER FLASHCACHE command cannot proceed. There may be data that is not synchronized to the grid disks (dirty data) in flash cache. Use the ALTER FLASHCACHE command to flush the dirty data and stop caching, and then run the ALTER FLASHCACHE command to resize or alter flash cache. The following cell disks need to be flushed: {0}.

Cause: The flash cache was not altered because the flash disks must be flushed before resizing the disks.

Action: Flush the flash disks, and then reissue the command after the flushing process is complete.

CELL-02861: The ALTER FLASHCACHE command requires at least one working flash cell disk.

Cause: There were no working flash cell disks on the system.

Action: Correct the failed flash cell disks, and then re-enter the command.

CELL-02862: Deactivation of grid disks failed due to reduced redundancy of the following grid disks: {0}.

Cause: The patchmgr utility encountered a problem. The grid disks were not deactivated because the other cell grid disks are not online.

Action: Ensure all partner disks are online before applying a rolling patch.

CELL-02863: Reactivation of grid disks timed out during patching process. The following grid disks are still offline: {0}.

Cause: The patchmgr utility encountered a problem. The grid disks were not reactivated during the patching process.

Action: Ensure all partner disks are online before applying a rolling patch.

CELL-02864: The patchmode parameter value {0} is invalid. The parameter must be set to {1} or {2}.

Cause: An invalid patchmode value was used in the command.

Action: Enter the command using a valid patchmode value.

CELL-02865: Downgrade cannot proceed due to following sparse grid disks detected on this cell. Drop them and retry. {0}

Cause: Sparse grid disks were detected during the downgrade procedure.

Action: Drop the listed grid disks, and retry the command.

CELL-02866: Failed to create sparse grid disk because sparse grid disk creation has been disabled by Oracle support.

Cause: The sparse grid disk was not created.

Action: This message is informational. No action is needed.

CELL-02867: Failed to create or alter sparse grid disk because the virtualSize is invalid.

Cause: The sparse grid disk was not created or altered.

Action: Enter the command using a valid value.

CELL-02870: Invalid IOTimeoutThreshold value. Enter a valid format, such as '2s'.

Cause: An invalid value was entered for the command.

Action: Enter the command using a valid value.

CELL-02871: Failed to alter IOTimeoutThreshold: {0}.

Cause: The timeout threshold was not changed.

Action: Check CELLSRV status, and then retry the command.

CELL-02872: String length for attribute dbPerfDataSuppress is too large ({0}), maximum string length allowed is {1}.

Cause: The string specified for the attribute was too long.

Action: Reduce the number of databases specified, or rename the databases using shorter names. The dbPerfDataSuppress attribute specifies which databases should not have their statistics reported in Automatic Workload Repository (AWR) reports.

CELL-02873: Not enough space left on celldisk {0}. At least 1 GB is needed.

Cause: There was less than 1 GB of space on the cell disk.

Action: Free some space on the cell disk, and retry the command.

CELL-02874: Erase data operation was stopped because physical disk status is warning - confinedOnline or warning - poor performance. Retry the operation after ensuring disk status is normal.

Cause: The erase operation was stopped because the disk status was poor.

Action: Retry the erase operation after ensuring that the disk status is normal.

CELL-02875: Failed to create or alter sparse grid disk because the requested physical size specified in the "size" parameter would exceed the maximum total physical size of 4 TB for all sparse grid disks on a cell disk.

Cause:The size specified for the sparse grid disk is too large.

Action: Retry the command using a smaller value for the size parameter or drop sparse grid disks to reduce the total physical size of all sparse grid disks to under 4 TB on the cell disk.

CELL-02876: To avoid conflicts, only one of the following attributes should be specified: {0}.

Cause: More than one value for the same quarantine entity was specified. This is for regular or consolidate database ID and name only. For example, because a quarantine creation entry needs only one attribute to identify a database, specifying both database ID and database name is not allowed.

Action: Specify only one attribute to identify the regular or consolidate database when creating a quarantine.

CELL-02891: Operation cannot be completed due to disk failure.

Cause: Disk has failed.

Action: Replace the disk, then retry the command.

CELL-02892: Operation cannot be completed due to temporary disk hang.

Cause: Disk IOs are temporarily hung, but the disk may recover.

Action: Retry the command.

CELL-02893: Operation cannot be completed due to IO errors.

Cause: The disk encountered an IO error.

Action: Replace the disk, then retry the command.

CELL-02894: Requested grid disk size is smaller than ASM disk size. Please resize ASM disk {0} first.

Cause: The grid disk size is smaller than the Oracle ASM disk size.

Action: Resize the Oracle ASM disk, and retry the command.

CELL-02895: Failed to retrieve size of ASM disk {0}. Please check if ASM instance is online and try again.

Cause: The size of the ASM disk could not be obtained from Oracle ASM.

Action: Verify the Oracle ASM instance is available, and retry the command.

CELL-02896: The specified command would result in a smaller grid disk size than the ASM disk size. Please retry the command and specify a size that is at least {0}M.

Cause:The size specified for the truncated grid disk, after rounding by cellsrv, would be smaller than the Oracle ASM disk size, which could cause mounting errors.

Action: Retry the command and specify a value for the truncated grid disk that is at least the minimum allowable size.

CELL-02897: OS group name is required to create a DXF disk.

Cause: The groupname attribute was not specified when creating the DXF grid disk.

Action: Retry creation command with a groupname attribute, for example CREATE GRIDDISK ALL prefix=DXFGD, groupname=root

CELL-02898: OS group does not exist. Please provide the name of an existing group.

Cause: When creating a DXF grid disk, an invalid groupname was specified (not registered in /etc/group).

Action: Retry creation command with a valid groupname.

CELL-02899: Local file name exceeds character limit. Please limit the file name to 64 characters.

Cause: When creating a DXF grid disk, the specified grid disk name contains too many characters, so that the resulting file name exceeds 64 characters. For example: CREATE GRIDDISK diskwithaverycomplicatedandverylengthyfilename1234098723450912340987135.

Action:Retry the command using a shorter grid disk name.

CELL-02902: ASM cluster name {0} cannot be empty, and cannot be longer than 14 characters.

Cause: The Oracle ASM cluster name is either empty, or contains too many characters.

Action: Ensure that the Oracle ASM cluster name contains less than 15 alphanumeric, hyphen, and plus characters.

CELL-02903: ASM cluster name {0} must contain only alphanumeric, hyphen, and plus characters.

Cause: The Oracle ASM cluster name contains an invalid character.

Action: Ensure that the Oracle ASM cluster name contains only alphanumeric, hyphen, and plus characters.

CELL-02904: ASM cluster name {0} matches an existing client, defined using "ASSIGN KEY", but its key differs. This is not allowed. To promote an existing client to an ASM cluster client, create it using the same key that was used to create it originally.

Cause: The specified name is already configured with a different key.

Action: You can change the cells in an Oracle ASM-scoped security to an ASMCLUSTER by running the ASSIGN KEY command with the same name, same key, and the ASMCLUSTER keyword. Use the LIST KEY command to view the existing keys.

CELL-02905: ASM cluster client {0} is still referenced by the "availableTo" attribute of the following active grid disks: {1}. An ASM cluster client cannot be altered while it is referenced by an active grid disk.

Cause: The ASM cluster client is referenced by the specified grid disks and cannot be altered.

Action: Remove the ASM cluster client from the grid disks first, or change the specified grid disks to be inactive using the ALTER GRIDDISK command.

CELL-02906: ASM cluster client {0} is referenced along with other clients in the "availableTo" grid disk attribute. Only one ASM cluster client can be referenced by a grid disk ACL.

Cause: The ASM cluster client should be the only client in the availableTo list.

Action: Make the grid disks available to only one ASM cluster.

CELL-02907: ASM cluster client {0} is referenced along with other clients in the "availableTo" grid disk attribute for existing grid disks: {1}. These grid disks should be corrected. If the grid disks are intended to be used by ASM cluster {0}, make them available to this cluster only, and not any other client.

Cause: The availableTo attribute specifies multiple clients (ASM cluster and others). It should specify only one client: the ASM cluster client.

Action: Make the grid disks available to only one ASM cluster.

CELL-02908: ASM cluster client {0} is still referenced by the "availableTo" attribute of the following grid disks: {1}. An ASM cluster client cannot be dropped while it is referenced by a grid disk.

Cause: The ASM cluster client cannot be dropped because it is referenced by the specified grid disks.

Action: Remove the ASM cluster client from the grid disks, then delete the ASM cluster client.

CELL-02919: Deactivation of grid disks failed because the respective ASM disk(s) are not offlined: {0}.

Cause: Attempted to deactivate grid disks but failed to offline the corresponding Oracle ASM disks.

Action: Make sure the grid disk attribute asmDeactivationOutcome for all corresponding Oracle ASM disks is Yes and try to deactivate grid disks again.

CELL-02920: The specified cell disk size {0} is larger than the LUN size {1}

Cause: Attempted to create a cell disk with a specified size that is larger than the LUN size

Action: Retry the command and specify a size that is smaller than the LUN size.

CELL-02924: The {0} attribute can only be changed by the root user.

Cause: Attempted to execute a command while not logged in as the root user

Action: Log in as the root user and retry the command

CELL-02925: Maximum size exceeded for the access control list.

Cause: Attempted to specify a value for the httpAccess attribute that exceeds the maximum limit

Action: Retry the command with less than 512 IP addresses.

CELL-02951: Size of the celldisk cannot exceed the smallest physical disk size of {0}.

Cause: You attempted to created a cell disk with a specified size that is larger than the maximum allowed size.

Action: Retry the command with a smaller size for the cell disk.

B.2.7 Error Messages: CELL-03001 to CELL-03500

These error messages are in the range CELL-03001 through CELL-03500.

CELL-03001: An exception occurred during ADR mining: {0}

Cause: An internal error occurred while searching for incidents in the Automatic Diagnostic Repository (ADR).

Action: Contact Oracle Support Services.

CELL-03002: Failed to parse value for key: {0}

Cause: An internal error occurred while searching for incidents in the Automatic Diagnostic Repository (ADR).

Action: Contact Oracle Support Services.

B.2.8 Error Messages: CELL-03501 to CELL-04000

These error messages are in the range CELL-03501 through CELL-04000.

CELL-03501: MSFK1HardwareImpl not initialized properly. Received exception: {0}

Cause: FK1 represents the fake hardware adapter class. This virtual hardware was only used for testing purposes and could not be initialized.

Action: Contact Oracle Support Services.

CELL-03502: MSHP1HardwareImpl not initialized properly. Received exception: {0}

Cause: A problem occurred with the HP1 hardware (HP1 is the cell hardware appliance code).

Action: Contact Oracle Support Services.

CELL-03503: MSHardwareImpl not initialized properly. Received exception: {0}

Cause: A problem occurred with the hardware (Oracle Exadata Storage Server).

Action: Contact Oracle Support Services.

CELL-03504: Cannot recognize appliance type: {0}

Cause: The cell hardware was not a recognized type.

Action: Contact Oracle Support Services.

CELL-03505: Cannot get appliance type: {0}

Cause: The cell hardware type was not obtained.

Action: Contact Oracle Support Services.

CELL-03506: Cannot configure BMC device on fake hardware.

Cause: This virtual hardware was only used for testing purposes and could not be configured.

Action: No action is required.

CELL-03507: MSIN1HardwareImpl not initialized properly. Received exception: {0}.

Cause: A problem occurred with the IN1 hardware (IN1 is the cell hardware appliance code).

Action: Contact Oracle Support Services.

CELL-03508: Exception raised during hardware poll: {0}.

Cause: A problem occurred with this hardware polling operation.

Action: Contact Oracle Support Services.

CELL-03511: MSSN1HardwareImpl not initialized properly. Received exception: {0}.

Cause: An exception occurred during the Sun hardware adapter initialization process.

Action: Examine the exception text for a possible solution. If a solution is not apparent, then contact Oracle Support Services.

B.2.9 Error Messages: CELL-04501 to CELL-05000

These error messages are in the range CELL-04501 through CELL-05000.

CELL-04501: Multiple responses received while expecting a single response for {0}.

Cause: An internal error occurred.

Action: Contact Oracle Support Services.

CELL-04502: Appliance type {0} is not recognized.

Cause: Invalid hardware was used for the cell or the hardware was not properly configured.

Action: Check the hardware configuration for the cell.

CELL-04503: PopulateDiskAdp not implemented for this hardware.

Cause: The hardware adapter was not completely implemented for this hardware.

Action: Contact Oracle Support Services.

CELL-04504: Partition append string not set for this appliance.

Cause: The hardware adapter was not completely implemented for this hardware.

Action: Contact Oracle Support Services.

CELL-04505: Function createSDL is not implemented

Cause: The hardware adapter was not completely implemented for this hardware.

Action: Contact Oracle Support Services.

CELL-04506: Failed to generate new unique cell disk name: {0}

Cause: An internal error occurred in the program.

Action: Contact Oracle Support Services.

CELL-04507: Function getOSNameForLun is not implemented in Hardware.

Cause: The hardware adapter was not completely implemented for this hardware.

Action: Contact Oracle Support Services.

CELL-04508: Cannot get validity check for a cell disk partition from CELLSRV.

Cause: CELLSRV and Management Server (MS) could not communicate with each other.

Action: Retry the command that was entered when the error occurred. If the problem persists, then try restarting the CELLSRV and MS services with the ALTER CELL command.

See Also:

ALTER CELL
CELL-04509: The LUN name cannot be found.

Cause: The specified LUN name was not found.

Action: Enter the LIST LUN command to display the names of the existing LUNs.

See Also:

LIST LUN
CELL-04510: Disk object {0} does not have ATTR_LUN set.

Cause: An internal error occurred. An error occurred in the vendor-specific controller utility.

Action: Contact Oracle Support Services.

CELL-04511: For LUN {0} cell disk is added {1}, Can Use LUN: {2}. Drop the cell disk with force and add it again.

Cause: A configuration problem was caused by the explicit use of the software RAID utility mdadm. Oracle Exadata System Software uses the mdadm utility for configurations made through Cell Server (CELLSRV). You should not change the software RAID configurations with this utility. If you change the default mdadm configurations, then there is a mismatch.

Action: Drop the cell disk with the FORCE option to delete the mismatched configuration. Re-create the cell disk to install the correct configuration.

CELL-04512: Invalid machine. Cannot create cell disk.

Cause: The cell was invalid.

Action: Contact Oracle Support Services.

CELL-04513: Cell Server (CELLSRV) cannot successfully add cell disk: {0}

Cause: The CELLSRV could not add the specified cell disk.

Action: Restart CELLSRV with the ALTER CELL command.

See Also:

ALTER CELL
CELL-04514: LUN name cannot be obtained while adding cell disk to configuration file.

Cause: An internal program error occurred.

Action: Contact Oracle Support Services.

CELL-04515: Disk object cannot be obtained for LUN: {0}

Cause: An internal program error occurred.

Action: Contact Oracle Support Services.

CELL-04516: LUN Object cannot be obtained for cell disk: {0}

Cause: An internal program error occurred.

Action: Contact Oracle Support Services.

CELL-04517: Cell Server (CELLSRV) cannot drop the cell disk.

Cause: The CELLSRV could not drop the specified cell disk.

Action: Drop the cell disk with the FORCE option. If that operation is not successful, then contact Oracle Support Services.

See Also:

DROP CELLDISK
CELL-04519: Cannot complete the drop of cell disk {0}. Received error: {1}. Cell disks not dropped: {2}.

Cause: The specified cell disks could not be dropped because there is flash cache or flash log.

Action: Drop the flash cache or flash log before dropping the cell disk, or specify the FORCE option to remove the flash cache and flash log, and drop the cell disk.

See Also:

DROP CELLDISK
CELL-04520: An existing celldisk entry is present for the LUN {0}.

Cause: The LUN already had a cell disk present.

Action: Determine the name of the cell disk that is present on the LUN; see LIST LUN. Drop this cell disk using the FORCE option if appropriate; see DROP CELLDISK.

CELL-04521: The LUN {0} has a valid cell disk (which is not imported).

Cause: The LUN already had a cell disk present.

Action: Use CREATE CELLDISK with the FORCE option to drop and create a new cell disk on this LUN.

See Also:

CREATE CELLDISK
CELL-04522: LUN {0} has a valid cell disk.

Cause: The LUN already had a cell disk present.

Action: Determine the name of the cell disk that is present on the LUN. Drop this cell disk using the FORCE option if appropriate. Then create a new cell disk on the LUN. Or use CREATE CELLDISK with the FORCE option to drop and create a new cell disk on this LUN.

CELL-04523: Object name not found in attribute.

Cause: An internal program error occurred.

Action: Contact Oracle Support Services.

CELL-04524: Physicaldisk object cannot be obtained for physical disk: {0}

Cause: An internal program error occurred.

Action: Contact Oracle Support Services.

CELL-04525: LUN object cannot be obtained for LUN: {0}

Cause: An internal program error occurred.

Action: Contact Oracle Support Services.

CELL-04526: Invalid type of object. Only LUN or physical disk can be provided as arguments for create celldisk.

Cause: An invalid object was provided as an argument for the CREATE CELLDISK command.

Action: Use CREATE CELLDISK with a valid LUN or physical disk attribute value.

See Also:

CREATE CELLDISK
CELL-04527: Cannot complete creation of cell disk {0}. Received error: {1} Cell disk not created on: {2}

Cause: A problem occurred when creating a cell disk on the named object.

Action: Use CREATE CELLDISK with the FORCE option.

See Also:

CREATE CELLDISK
CELL-04528: Non-Single-Disk LUN found and needs to be reenabled. CREATE CELLDISK ALL cannot enable non-single-disk LUNs.

Cause: The cells support only single-disk LUNs.

Action: Remove the non-single-disk LUN, then use CREATE CELLDISK with the ALL option.

See Also:

CREATE CELLDISK
CELL-04529: A failed LUN cannot be enabled.

Cause: An internal error occurred.

Action: Contact Oracle Support Services.

CELL-04530: Physical disk {0} to be removed was not found in the list.

Cause: An internal error occurred.

Action: Contact Oracle Support Services.

CELL-04531: Error encountered while creating Single Disk LUN (SDL) on physical disk: {0}. Received error: {1} Cell disk not created: {2}

Cause: An internal error occurred.

Action: Contact Oracle Support Services.

CELL-04532: Error encountered while creating cell disk on: {0}.

Cause: An internal error might have occurred.

Action: The error text explains the error condition. Follow the recommended steps, if any, in the error text. If no steps are provided, then contact Oracle Support Services.

CELL-04534: Non-Single Disk LUN found on physical disk: {0}

Cause: A non-single-disk LUN was found on the physical disk.

Action: Remove the non-single-disk LUN from the specified physical disk.

CELL-04535: No LUN object found for the created SDL on: {0}

Cause: An internal error occurred.

Action: Contact Oracle Support Services.

CELL-04536: The command {0} returned an exit status: {1}.

Cause: An internal error could have occurred.

Action: The error text explains the error condition. Follow the recommended steps (if any) in the error text. If no steps are provided, then contact Oracle Support Services.

CELL-04537: Cannot get disk controller Id.

Cause: An unsupported version was used on the vendor-specific controller utility.

Action: Contact Oracle Support Services.

CELL-04538: Physical disk {0} is part of a non-Single Disk LUN. Cannot delete it to create a Single Disk LUN.

Cause: A non-single disk LUNs was present on a physical disk.

Action: Remove the non-single disk LUN manually using the vendor specific controller utility.

CELL-04539: Cannot create single-disk LUN on physical disk {0} because there is already a LUN on this physical disk.

Cause: A LUN was already on this physical disk.

Action: Use the FORCE option if you want to overwrite an existing LUN.

CELL-04541: Operating system name for LUN {0} not found.

Cause: An error occurred in the vendor-specific controller utility.

Action: Contact Oracle Support Services.

CELL-04543: Invalid physical drive Id for: {0}

Cause: An invalid ID was entered for the specified physical disk.

Action: Use the LIST PHYSICALDISK pdisk_name command to display the ID for the specified physical disk.

CELL-04544: Invalid Id for LUN: {0}

Cause: An invalid ID was entered for the specified LUN.

Action: Use the LIST LUN lun_name command to display the ID for the specified LUN.

See Also:

LIST LUN
CELL-04545: Exception in Disk Adapter: {0}

Cause: A problem occurred with the disk adapter.

Action: Contact Oracle Support Services.

CELL-04546: The command {0} returned an exit code of {1}. Kill any other instances of hpacucli processes.

Cause: A problem occurred with the disk configuration tool process.

Action: Contact Oracle Support Services.

CELL-04547: Cell Server (CELLSRV) cannot successfully export cell disk: {0}.

Cause: A problem occurred when exporting the cell disk.

Action: Contact Oracle Support Services.

CELL-04548: Cannot export cell disk {0} because its status is not normal.

Cause: Because the status of the cell disk was not normal, the cell disk could not be exported.

Action: Contact Oracle Support Services.

CELL-04549: Cannot obtain LUN for cell disk: {0}.

Cause: The LUN could not be accessed for the specified cell disk.

Action: Contact Oracle Support Services.

CELL-04550: Export is not implemented for this hardware.

Cause: The export function was not implemented on the hardware.

Action: Contact Oracle Support Services.

CELL-04551: Error encountered during export of cell disk {0}. Received error: {1}. Cell disks not exported: {2}

Cause: Because of an error, the cell disk had not been exported.

Action: Contact Oracle Support Services.

CELL-04552: Cell Server (CELLSRV) could not rescan: {0}.

Cause: CELLSRV could not rescan the specified LUN.

Action: Contact Oracle Support Services.

CELL-04553: Could not import {0} because of a preexisting cell disk named {0}.

Cause: The LUN could not be imported because there was an existing cell disk with the same name as the cell disk to be imported.

Action: Contact Oracle Support Services.

CELL-04554: Cell Server (CELLSRV)cannot successfully import the LUN: {0}.

Cause: CELLSRV could not import the specified LUN.

Action: Contact Oracle Support Services.

CELL-04555: Cell Server (CELLSRV) cannot rename imported cell disk {0}.

Cause: CELLSRV could not rename the imported cell disk with the supplied cell disk name.

Action: Contact Oracle Support Services.

CELL-04556: LUN {0} does not contain a valid cell disk.

Cause: The specified LUN did not contain a valid cell disk.

Action: Contact Oracle Support Services.

CELL-04557: LUN could not be obtained for {0}.

Cause: The LUN with the specified attribute could not be accessed.

Action: Contact Oracle Support Services.

CELL-04558: LUN must be used to identify the import target.

Cause: The LUN ID must be specified to identify the cell disk to be imported.

Action: Use the LUN=lun_id option with IMPORT CELLDISK.

CELL-04559: Cannot complete import of cell disk on LUN {0}. Received Error: {1}.

Cause: An error occurred when trying to import the cell disk on the specified LUN.

Action: Contact Oracle Support Services.

CELL-04560: Cannot complete import of cell disk {0}. Received Error: {1}. Cell disks not imported: {2}.

Cause: An error occurred when trying to import the cell disk.

Action: Contact Oracle Support Services.

CELL-04570: Internal MS error due to a mismatch of software and hardware. Contact Oracle Support Services.

Cause: Software and hardware did not match.

Action: Contact Oracle Support Services.

CELL-04571: The command {0} returned error string {0}.

Cause: An error occurred when running the command.

Action: Review the error string to determine the cause of the error. Re-enter the command or Contact Oracle Support Services.

CELL-04572: Could not determine slot number for physical drive {0}.

Cause: The disk configuration tool process cannot determine the slot number for this physical drive.

Action: Contact Oracle Support Services.

CELL-04573: Could not determine slot number for Logical drive {1}.

Cause: The disk configuration tool process cannot determine the slot number for this logical drive.

Action: Contact Oracle Support Services.

CELL-04574: LUN {0} is in state {1} and is a system disk. Use the FORCE option to resync the multiple disk devices on the system disks.

Cause: The FORCE option was not used when re-enabling the LUN.

Action: Use the FORCE option with ALTER LUN REENABLE.

See Also:

ALTER LUN
CELL-04575: Could not determine slot OR serial number for ctrl {0}.

Cause: The disk configuration tool process cannot determine the slot number for this controller.

Action: Contact Oracle Support Services.

CELL-04576: The command {0} returned error string {1}.

Cause: A program error occurred.

Action: Contact Oracle Support Services.

CELL-04577: LUN {0} could not find a corresponding physical disk.

Cause: The physical disk corresponding to the specified LUN could not be found.

Action: Insert the physical disk corresponding to the specified LUN.

CELL-04578: LED action was not taken as disk {0} status is {1}.

Cause: An attempt was made to turn off the Fault-Service Required LED light for a disk that had failed, or had poor performance.

Action: Contact Oracle Support Services to fix the disk problem. After the disk is fixed, the Fault-Service Required LED light can be turned off.

CELL-04579: Cannot alter Flash Disk LED. Please refer to 'help alter physicaldisk'.

Cause: The Flash Disk LED was not altered.

Action: Refer to the help file, and ALTER PHYSICALDISK.

CELL-04580: LUN {0}, physical disk {1} is in state {2} and cannot be re-enabled. It must be replaced.

Cause: The physical disk cannot be re-enabled.

Action: Replace the physical disk.

CELL-04582: An error was encountered while populating the disk.

Cause: An error was encountered while populating the disk.

Action: Contact Oracle Support Services.

CELL-04583: Cannot re-enable LUN on physical disk in slot {0} (serial number: {1}) because its disk model number {2} is not supported.

Cause: The physical disk had an unsupported model number.

Action: Contact Oracle Support Services.

CELL-04585: Cannot retrieve the current disk status.

Cause: The current disk status could not be retrieved.

Action: Contact Oracle Support Services.

CELL-04586: Cell disk creation was not successful.

Cause: An error was encountered when creating the cell disk.

Action: Review the list of errors for the reason cell disk creation was not successful.

CELL-04589: An invalid setting was specified for the failure type attribute. Specify a valid failure type (FAILED, PREDICTIVEFAILURE, WTCACHING or NONE).

Cause: An invalid failure type was specified.

Action: Specify a valid failure type, and retry the ALTER PHYSICALDISK command. The valid failure types are FAILED, PREDICTIVEFAILURE, WTCACHING or NONE.

CELL-04590: Failure type {2} cannot be simulated on disk {0} of type {1}. Only flash disks can be simulated to be in "WriteThrough Caching" status.

Cause: A hard disk or M.2 disk was specified to be in write through caching mode.

Action: Specify a flash disk in the ALTER PHYSICALDISK command.

CELL-04591: "alter physicaldisk serviceled on/off" is obsolete. Use "alter physicaldisk drop for replacement" if you want to proactively replace a disk.

Cause: The SERVICELED ON/OFF option for the ALTER PHYSICALDISK command is no longer supported.

Action: Use the DROP FOR REPLACEMENT option when you need to replace a disk. See ALTER PHYSICALDISK for details.

CELL-04592: Cannot drop physical disk {0} because it is not ready to be removed

Cause: The disk was not in a drop ready state.

Action: Run ALTER PHYSICALDISK diskname DROP FOR REPLACEMENT before running the DROP PHYSICALDISK command.

CELL-04593: Cannot drop system disk {0}

Cause: The specified disk was a system disk, which cannot be dropped.

Action: Specify a non-system disk in the DROP PHYSICALDISK command.

CELL-04594: Cannot decrease maximum number of supported physical disks below {0}

Cause: If the specified disks were dropped, the total number of supported disks would be below the maximum number of supported physical disks.

Action: Specify fewer physical disks to drop in the DROP PHYSICALDISK command.

CELL-04595: Physical disks must be dropped in following order: {0}

Cause: Physical disks were specified in an incorrect order.

Action: Specify physical disks in the correct order in the DROP PHYSICALDISK command.

CELL-04601: Dropping physical disks was not successful: {0}

Cause: The physical disks were not dropped by the command.

Action: The physical disks specified in error message CELL-04602 were not dropped. Resolve the problems described in error message CELL-04602, and then drop the physical disks.

CELL-04602: An error encountered while dropping physical disk {0}. Received error: {1}.

Cause: An error was encountered while dropping the physical disk.

Action: Resolve the problem described by the error before dropping the physical disk.

CELL-04603: Cannot drop flashdisk {0} for replacement.

Cause: The DROP command was used for flash disk.

Action: The DROP command is not valid for flash disks.

CELL-04604: Cannot drop physical disk {0} because it was already removed.

Cause: The DROP command is not valid because the physical disk was removed.

Action: Confirm that the physical disk is present, and then run the ALTER PHYSICALDISK DROP FOR REPLACEMENT command.

CELL-04605: The other system disk is worse.

Cause: The disk could not be dropped due to problems with the other system disk.

Action: Drop and replace the system disk before dropping and replacing the specified disk.

CELL-04606: MD is not in sync.

Cause: The disk was not dropped because multiple devices were not synchronized.

Action: Wait until all the multiple devices are synchronized before dropping and replacing the specified disk.

CELL-04607: Disk {0} has unhealthy partner disk: {1}.

Cause: The disk could not be dropped due to a problem with the partner disk.

Action: Do one of the following actions on the unhealthy partner disk before dropping and replacing the specified disk:

  • Bring the unhealthy partner disk online.

  • Drop and replace the disk that has the unhealthy partner disk.

CELL-04608: Re-enabling physical disks was not successful: {0}.

Cause: The re-enabling of the physical disks was not successful.

Action: The physical disks specified in error message CELL-04609 are not re-enabled. Resolve the problems described in error message CELL-04609, and then re-enable the physical disks.

CELL-04609: An error was encountered while re-enabling physical disk {0}. Received error: {1}.

Cause: An error was encountered while re-enabling the disk.

Action: Resolve the problem described by the error before re-enabling the physical disk.

CELL-04610: Re-enable is not allowed for disk {0}. The ALTER PHYSICALDISK REENABLE command can only re-enable disks that are dropped for replacement.

Cause: The disk was not re-enabled because it was not dropped using the ALTER PHYSICALDISK DROP FOR REPLACEMENT command.

Action: Confirm that the physical disk was dropped, and then run the ALTER PHYSICALDISK REENABLE command.

CELL-04611: Cannot re-enable physical disk {0} because it is in wrong slot.

Cause: The physical disk was inserted into the wrong slot.

Action: Use the ALTER PHYSICALDISK REENABLE command with the FORCE option to re-enable the disk.

CELL-04613: Cannot re-enable physical disk {0} because it is not normal.

Cause: The disk was not re-enabled because there is a problem with the disk.

Action: Replace the hard disk.

CELL-04614: An error was encountered while creating LUN on physical disk {0}.

Cause: An error was encountered while creating the LUN on the physical disk.

Action: Run the ALTER LUN command. If the command fails, then replace the disk.

CELL-04615: An error was encountered while re-enabling LUN on physical disk {0}.

Cause: An error was encountered while re-enabling the LUN on the physical disk.

Action: Run the ALTER PHYSICALDISK REENABLE command. If the command fails, then replace the disk.

CELL-04616: An error was encountered while updating firmware for physical disk {0}.

Cause: An error occurred while updating the firmware.

Action: Update the disk firmware, and retry the command.

CELL-04617: Re-enabling LUNs was not successful: {0}.

Cause: The LUNs were not re-enabled.

Action: Fix the error that is causing the re-enable operation to failed, and then retry the command.

CELL-04618: An error was encountered while re-enabling LUN {0}.

Cause: Not all LUNs were enabled successfully.

Action: Fix the error that is causing the re-enable operation to failed, and then retry the command.

CELL-04619: An error was encountered while validating cell disk on physical disk {0}.

Cause: The physical disk could not be accessed to read the cell disk metadata.

Action: Ensure the physical disk can be accessed, and retry the command.

CELL-04620: Re-enabling the LUN {0} is not allowed. The ALTER LUN REENABLE command can only re-enable LUNs that are in "poor performance" status.

Cause: The ALTER LUN REENABLE command could not re-enable the LUN because the LUN was not in poor performance status.

Action: Run the ALTER LUN REENABLE FORCE command to re-enable the LUN.

CELL-04621: Physical disk {0} is in state {1} and cannot be reenabled. It must be replaced.

Cause: The physical disk cannot be re-enabled.

Action: Replace the disk.

CELL-04622: Physical disk {0} is in state {1} and cannot be re-enabled.

Cause: The physical disk was in a confined state.

Action: Wait for the physical disk to change to a non-confined state, and then retry the ALTER PHYSICALDISK REENABLE command.

CELL-04623: Power cycling physical disks was not successful: {0}.

Cause: The power cycle operation failed for the disks.

Action: Contact Oracle Support Services.

CELL-04624: An error was encountered while power cycling physical disk {0}. Received error: {1}.

Cause: The power cycle operation failed for the specified error for the disks.

Action: Correct the problem specified by the error.

CELL-04625: Power cycling physical disks is not supported on storage servers earlier than X5 servers.

Cause: Power cycle is not supported for physical disks earlier than Oracle Exadata Database Machine X5-2 servers.

Action: The powercycle option is not available for the physical disk.

CELL-04626: Cannot power cycle flash disk {0}.

Cause: Power cycle is not supported for flash disks earlier than Oracle Exadata Database Machine X5-2 servers.

Action: The powercycle option is not available for the flash disk.

CELL-04627: Physical disk {0} is in state {1} and cannot be power cycled.

Cause: The power cycle operation was not done on the dis because the disk was in a confined state.

Action: Wait until the confinement test completes on the disk, and then re-enter the command.

CELL-04628: Power cycling physical disks is disabled for this cell.

Cause: The powercycle option was disabled for this cell.

Action: Enable the powercycle option on the cell.

CELL-04629: Physical disk {0} is not in failed state.

Cause: The power cycle command was entered for the disk, but the physical disk was not in a failed state.

Action: Enter the command, and specify a failed physical disk.

CELL-04630: Physical disk {0} power cycle count exceeds the maximum allowed and FORCE not specified.

Cause: The disk was power cycled the maximum number of times.

Action: Use the FORCE option to power cycle the disk.

CELL-04643: The other system disk's status is not normal. Replace the other system disk and try again.

Cause: You attempted to offline a system disk when the other system disk did not have a status of NORMAL.

Action: Replace the bad system disk and retry this operation.

CELL-04644: Cannot power cycle M.2 disk {0}.

Cause: The power cycle command was entered for a M.2 disk.

Action: M.2 disks cannot be power cycled.

CELL-04645: Cannot create cell disk on disk of type {0}.

Cause: You attempted to create a cell disk on an unsupported disk type.

Action: Create the cell disk on a supported disk type.

CELL-04646: Crypto erasure failed on the following qualified cell disks: {0}.

Cause: An error was encountered when attempting to use Secure Eraser on the cell disks being dropped.

Action: Review the log files to determine the cause of the error. Correct the problem and try the command again.

B.2.10 Error Messages: CELL-05001 to CELL-05500

These error messages are in the range CELL-05001 through CELL-05500.

CELL-05001: Error code returned while executing: {0}

Cause: A program error occurred.

Action: Contact Oracle Support Services.

CELL-05002: Exception occurred while executing: <program>

Cause: A program exception occurred.

Action: Contact Oracle Support Services.

CELL-05003: Error encountered while opening or reading {0}. The content of {1}:{2}. Error: {3}.

Cause: A program error occurred.

Action: Contact Oracle Support Services.

CELL-05005: Illegal value for interval specified to find the average CPU queue length.

Cause: A program error occurred.

Action: Contact Oracle Support Services.

CELL-05006: Line returned by checkdev can not be parsed: {0}.

Cause: An internal string generated by the hardware and firmware checker tool could not be parsed.

Action: Contact Oracle Support Services.

CELL-05008: VALIDATE CONFIGURATION failed, but this command may succeed if retried after a few minutes. Error: {0}.

Cause: The VALIDATE CONFIGURATION command failed.

Action: Retry the command after a few minutes.

CELL-05009: System logger command returns error: {0}.

Cause: The validate syslogconf operation encountered an error while trying to send a message on the configured logger.

Action: Review the syslogConf settings, correct any configuration errors, and then re-enter the command.

CELL-05010: service syslog restart returns error: {0}.

Cause: The validate syslogconf operation encountered an error while trying to restart the configured logger.

Action: Review the syslogConf settings, correct any configuration errors, and then re-enter the command.

CELL-05011: An error occurred while writing the syslog.conf file: {0}.

Cause: An error was encountered while trying to write the syslog.conf file to configure the syslog service.

Action: Contact Oracle Support Services.

CELL-05012: VALIDATE CONFIGURATION failed with I/O error : {0}

Cause: The VALIDATE CONFIGURATION command failed.

Action: Contact Oracle Support Services.

B.2.11 Error Messages: CELL-05501 to CELL-06000

These error messages are in the range CELL-05501 through CELL-06000.

CELL-05501: Invalid mail configuration. Please make sure smtpServer, smtpFromAddr and smtpToAddr are set before verify the mail configuration. In addition, in order to get mail notifications for alerts, notificationPolicy should be set properly. A valid command could be: alter cell smtpServer='mailserver.example.com', smtpfromAddr='yourname@example.com', smtptoAddr='yourname@example.com', notificationPolicy=critical, notificationMethod=mail

Cause: An invalid value was entered for an e-mail configuration attribute.

Action: Set the values for the smtpServer, smtpFromAddr, smtpToAddr, notificationMethod, and notificationPolicy attributes with the ALTER CELL command before verifying the mail configuration.

See Also:

"ALTER CELL"

CELL-05503: An error was detected during notification. The text of the associated internal error is: {0}. The notification recipient is {1}.

Cause: A problem occurred when processing the notification.

Action: Ensure that the recipient is valid. Check the toAddr cell attribute.

See Also:

CELL-05504: An error was detected during ASR notification. The text of the associated error is: {0}. The notification recipient is {1}.

Cause: An error was detected during the sending of an ASR SNMP notification.

Action: Check that the recipient is specified correctly. If the recipient is incorrect, the use the ALTER CELL snmpSubscription command to correct the recipient information. If the recipient is correct and the error continues to occur, then contact Oracle Support Services.

CELL-05505: Errors were detected during ASR validate: {0}.

Cause: An error was detected while sending an ASR SNMP notification for the ALTER CELL VALIDATE SNMP command.

Action: Check that the recipient is specified correctly. If the recipient is incorrect, the use the ALTER CELL snmpSubscription command to correct the recipient information. If the recipient is correct and the error continues to occur, then contact Oracle Support Services.

B.2.12 Error Messages: CELL-06001 to CELL-06200

These error messages are in the range CELL-06001 through CELL-06200.

CELL-06001: User does not exist: {0}.

Cause: The user specified in the command did not exist.

Action: Enter the command specifying a valid user.

CELL-06002: The user {0} already exists.

Cause: The user specified in the command was already created.

Action: Enter the command specifying a new user.

CELL-06003: Cannot create user {0} because it is a reserved user.

Cause: The name entered was a reserved user name.

Action: Enter the command with a different user name.

CELL-06004: Only one user can be specified in the command.

Cause: More than one user was specified in the command.

Action: Enter the command with only one user name.

CELL-06005: The attributes name and password must be included when creating a new user.

Cause: A user name and password were not specified while creating the user.

Action: Enter the command with a user name, and enter the password when prompted.

CELL-06006: Only the name and password attributes can be specified in the CREATE USER command

Cause: Additional attributes were specified in the CREATE USER command.

Action: Enter the command using only the user name and password.

CELL-06007: Valid user passwords are 8 to 40 alphanumeric characters or special characters (!@#$%^&*()-_) with at least one digit, one lowercase letter and one uppercase letter. The new password can not be the same as the current password for the user.

Cause: Password was not valid.

Action: Enter a password that contains 8 to 40 alphanumeric characters or special characters !@#$%^&*()-_ with at least one digit, one lowercase letter and one uppercase letter. Do not specify the same password that is currently set for the user.

CELL-06008: Failed to create password.

Cause: A password was not created.

Action: Retry the command specifying a valid password format.

CELL-06009: No privilege specified.

Cause: A privilege attribute was not specified in the command.

Action: Enter the command, and specify a privilege attribute.

CELL-06010: No role specified.

Cause: No role attribute was specified in the command.

Action: Enter the command, and specify a role attribute.

CELL-06011: Role does not exist: {0}.

Cause: An invalid role attribute was specified in the command.

Action: Enter the command with a valid role attribute.

CELL-06012: No user specified.

Cause: No user name was specified in the command.

Action: Enter the command, and specify a user name.

CELL-06013: The role {0} already exists.

Cause: The role specified in the CREATE command already existed.

Action: Enter the command with a new role attribute.

CELL-06014: No attribute or option is specified for this privilege.

Cause: No attributes or options were specified in the command.

Action: Enter the command, and specify attributes and options.

CELL-06015: Current user does not have privileges to run this command.

Cause: The user did not have the privileges to run the command.

Action: You do not have privileges to run the command.

CELL-06016: Privilege [{0}] cannot be revoked from role {1} because it is not defined for role {1}.

Cause: The privilege was not defined for that role.

Action: Enter the command with the correct role and privilege.

CELL-06017: Cannot drop role {0} because at least one user has this role. Retry command with FORCE option.

Cause: At least one user was granted this role.

Action: Retry the DROP command using the FORCE option.

CELL-06018: Cannot revoke privilege from some roles: {0}.

Cause: The privilege was not revoked for those roles.

Action: Review the error detail for additional information.

CELL-06019: Cannot drop some roles: {0}.

Cause: The role was not dropped.

Action: Review the error detail for additional information.

CELL-06020: Cannot drop user {0} because it is a reserved user.

Cause: You attempted to drop a reserved user.

Action: Enter the command with the correct user.

CELL-06021: Cannot drop the users because no users will remain with privilege to modify the cell access level.

Cause: You attempted to drop the last user with a specific access-level privilege.

Action: Enter the command with the correct user or drop the privilege first, then drop the users.

B.3 Alert Messages

This section describes the alert messages. This section contains the following topics:

B.3.1 Format of Alert Messages for E-mail Notification

Alert messages can be sent through email.

The format of an e-mail notification for an alert message is as follows:

Subject: 
cell_name: alert level: { critical | warning | clear } alert

E-mail Content:
Alert Type: { ADR | Hardware | Threshold } Alert alert_name is triggered at
alert_time with message:
alert_message

The suggested action is: 
alert_action

B.3.2 Format of Alert Messages for SNMP Notification

Simple Network Management Protocol (SNMP) alerts sent by Oracle Exadata Storage Servers conform to a Management Information Base (MIB) which is included in each Oracle Exadata System Software installation.

The MIB file on Oracle Exadata Storage Server is available at /opt/oracle/cell/cellsrv/deploy/config/cell_alert.mib. The SNMP alerts and MIB conform to SNMP version 1 (SNMPv1). The alerts contain variables, such as those shown in the following list.

  • oraCellAlertAction: Recommended action to perform for this alert.

  • oraCellAlertBeginTime: Time stamp when an alert changes state.

  • oraCellAlertEndTime: Time stamp for the end of the period when an alert changes state.

  • oraCellAlertExaminedBy: Administrator who reviewed the alert.

  • oraCellAlertMsg: Brief explanation of the alert.

  • oraCellAlertNotif: Number indicating progress in notifying subscribers to alert messages:

    • 0: Never tried

    • 1: Sent successfully

    • 2: Retrying, up to five times

    • 3: Five failed retries

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

  • oraCellAlertSeqBeginTime: Time stamp when an alert sequence ID is first created.

  • oraCellAlertSeqID: Unique sequence ID for the alert. When an alert changes state, such as from 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.

  • oraCellAlertSeverity: Severity level. Values are clear, info, warning, or critical.

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

  • oraCellAlertType: Type of the alert. Values are stateful or stateless.

    • Stateful alerts are automatically cleared on transition to normal.

    • Stateless alerts are never cleared.

B.3.3 Threshold Alert Messages

Threshold alerts help you monitor your database. Most alerts notify you when particular metric thresholds are exceeded.

For each alert, you can set critical and warning threshold values. These threshold values are boundary values that when exceeded, indicate that the system is in an undesirable state. For example, when a tablespace becomes 97 percent full, this can be considered undesirable, and Oracle Database generates a critical alert. The following are examples of threshold alerts:

Threshold name triggered alert state severity

The threshold alert was triggered. Examine the metric value that is violating the specified threshold. Correct the problem indicated by threshold name.

The threshold value is no longer violated. No further action is required for threshold name.

The threshold alert was cleared.

B.3.4 ADR Alert Messages

Problems are tracked in the Automatic Diagnostic Repository (ADR). ADR is a file-based repository for storing diagnostic data.

Because this repository is stored outside the database, the diagnostic data is available even when the database is down. Starting with Oracle Database release 11g, the alert log, all trace and dump files, and other diagnostic data are also stored in ADR.

Each problem has a problem key, which is a text string that describes the problem. The problem key includes the error code (such as ORA 00600), and in some cases, one or more error parameter values or other information. The following is an example of an ADR message:

Errors in file /opt/oracle/log/diag/asm/cell/stado54/trace/svtrc_2763_0.trc 
 (incident=1): ORA-00600: internal error code, arguments: [main_5], [3], 
[Invalid IP Param], [], [], [], [], []

The action to be taken for ADR messages is:

Create an incident package for incident <incident number> using ADRCI 
and upload the incident packages to Oracle Support Services.

B.3.5 Software Alert Messages

This section describes the Oracle Exadata System Software alerts.

SALRT-00001: MS has written its configuration file successfully.

Cause: Management Server (MS) successfully wrote the configuration file.

Action: No action is required.

SALRT-00003: The cell configuration check was successful.

Cause: The cell configuration check ran successfully.

Action: No action is required.

SALRT-00004: Configuration check discovered the following problems: {0}.

Cause: There was a problem during the cell configuration check.

Action: Correct the configuration problems. Then rerun the command listed.

SALRT-00007: Hugepage allocation was successful in service CELLSRV.

Cause: Huge page allocation was successful.

Action: No action is required.

SALRT-00008: Cell USB was restored from a failure.

Cause: The Oracle Exadata System Software CELLBOOT USB flash drive was restored.

Action: No action is required.

SALRT-00020: [WARNING] The USB has build problems. Attempts to repair it in the background failed.

Cause: The CELLBOOT USB flash drive failed due to a file system or hardware problem.

Action: Replace the CELLBOOT USB flash drive.

SALRT-00052: A quarantine has been automatically removed due to software upgrade.

Cause: The quarantine was automatically dropped due to a software upgrade.

Action: This message is informational. No action is needed.

SALRT-00061: ILOM has stopped responding, and did not reset after issuing reset commands.

Cause: The ILOM did not respond to the ipmitool mc reset cold or ipmitool sunoem cli reset -script /SP commands.

Action: Manual intervention is necessary to power cycle the ILOM. Use SSH to connect to the ILOM from this cell or another machine. At the ILOM prompt, enter reset /SP. If unable to connect using SSH, then try resetting the ILOM server by logging in to ILOM or remote console. To log in, go to Maintenance, and select ResetSP, and then click ResetSP. If that also does not work, then unplug the ILOM power supply. This action power cycles the server as well as the ILOM. Refer to My Oracle Support note 1395747.1 for additional information.

SALRT-00062: ILOM is back to a normal state.

Cause: The ILOM responded normally.

Action: This message is informational. No action is needed.

SALRT-00081: At least one essential file on the CELLBOOT USB flash drive fails the checksum check. See details in /var/log/cellos/checkdeveachboot.log.

Cause: One or more files failed the checksum process.

Action: Recreate the CELLBOOT USB flash drive.

See Also:

Oracle Exadata Database Machine Maintenance Guide for information about recreating the flash drive
SALRT-00082: Grub configuration file failed validation. See details in /var/log/cellos/checkdeveachboot.log.

Cause: The configuration file failed validation.

Action: Recreate the CELLBOOT USB flash drive.

See Also:

Oracle Exadata Database Machine Maintenance Guide for information about recreating the flash drive
SALRT-00083: Grub configuration file failed validation. See details in /var/log/cellos/checkdeveachboot.log. Failed file is grub/grub.conf.

Cause: The configuration file failed validation.

Action: Recreate the CELLBOOT USB flash drive.

See Also:

Oracle Exadata Database Machine Maintenance Guide for information about recreating the flash drive
SALRT-00084: The checksum list file, /checksums_cellboot_usb_files.txt, is not on the CELLBOOT USB flash drive.

Cause: The checksum list file was not on the CELLBOOT USB flash drive.

Action: Recreate the CELLBOOT USB flash drive.

See Also:

Oracle Exadata Database Machine Maintenance Guide for information about recreating the flash drive
SALRT-00087: No configuration inconsistencies found for flash cache mode.

Cause: No inconsistencies were found for the flash cache mode settings.

Action: This message is informational. No action is needed.

SALRT-00088: A kernel crash has rebooted the system.

Cause: A kernel crash caused the system to restart.

Action: The core file from the crash is at {0}. When requesting support, provide the core file to Oracle Support Services.

SALRT-00089: Celldisk {0} at device {1} cannot be used because of metadata corruption.

Cause: Cell disk metadata corruption was detected.

Action: The cell disk is unusable because of metadata corruption. Drop and recreate the cell disk, or contact Oracle Support Services.

SALRT-00090: Metadata corruption in the celldisk has been fixed.

Cause: The metadata corruption in the cell disk was fixed.

Action: This message is informational. No action is needed.

SALRT-00105: The download for update {0} failed.

Cause: The scheduled software update was not able to download the software update files from the location specified by the store attribute.

Action: Correct any download server issues and verify that the SoftwareUpdate store attribute URL is valid.

SALRT-00107: The prerequisite check for update {0} failed.

Cause: The prerequisite check for the scheduled software update failed.

Action: Correct the problems shown in the attached log files, then run the CellCLI command ALTER SOFTWAREUPDATE VALIDATE PREREQ. Verify that these problems are fixed.

SALRT-00109: The software update for {0} failed.

Cause: The scheduled software update failed.

Action: Correct the problems shown in the attached log files. Run the command ALTER SOFTWAREUPDATE UPGRADE and verify that these problems are fixed.

SALRT-00119: The {0} file contains a corrupted value of {1} for the httpsAccess attribute.

Cause: The {0} file contains a corrupted value of {1} for the httpsAccess attribute.

Action: For security reasons, the httpsAccess value was reset to NONE. Please use the ALTER {CELL | DBSERVER} command to change this value.

It is suspected that the value was corrupted by manually modifying the {1} file and other attributes might also have been affected.

Please contact Oracle Support Services.

SALRT-00120: The value {1} found for the httpsAccess attribute in the {0} file exceeds the maximum size limit of {2} for the access control list.

Cause: The value {1} found for the httpsAccess attribute in the {0} file exceeds the maximum size limit of {2} for the access control list.

Action: For security reasons, the httpsAccess value was reset to NONE. Please use the ALTER DBSERVER or ALTER CELL command to change this value.

It is suspected that the value was corrupted by manually modifying the {1} file and other attributes might also have been affected.

Please contact Oracle Support Services.

SALRT-10051: Advanced Intrusion Detection Environment (AIDE) detected potential changes to software on this system. The changes are in /var/log/aide/aide.log.

Cause: Advanced Intrusion Detection Environment (AIDE) violation encountered.

Action: Review the file /var/log/aide/aide.log and make a decision on whether the changes are expected. If the changes are expected, you may clear this alert by regenerating a new Intrusion Detection database by logging in as root and running

# /opt/oracle.SupportTools/exadataAIDE -u

AIDE will update its database and the alert will be cleared. If the changes are not expected, the system or security administrator should investigate the changes as a possible intrusion.

SALRT-10052: Advanced Intrusion Detection Environment (AIDE) violation has been cleared.

Cause: Advanced Intrusion Detection Environment (AIDE) violation has been cleared.

Action: Informational.

B.4 Contacting Oracle Support Services

Some messages recommend contacting Oracle Support Services to report a problem. You may also want to contact Oracle Support Services when you have a service request submitted by Auto Service Request. When you contact Oracle Support Services, have the following information available:

  • The hardware, operating system, and release number of the operating system running Oracle Database.

  • The complete release number of Oracle Database, such as release 11.2.0.3.

  • All Oracle programs (with release numbers) in use when the error occurred, such as SQL*Plus release 11.2.0.1.0.

  • If you encountered one or more error codes or messages, then the exact code numbers and message text, in the order in which they appeared.

  • The problem severity, according to the following codes:

    • 1: Program not usable. Critical effect on operations.

    • 2: Program usable. Operations severely restricted.

    • 3: Program usable with limited functions. Not critical to overall operations.

    • 4: Problem circumvented by customer. Minimal effect, if any, on operations.

You are also expected to provide the following:

  • Your name

  • The name of your organization

  • Your Oracle Support ID number

  • Your telephone number