D Error Messages for Oracle Exadata Database Machine and Oracle Exadata Rack

This appendix contains the hardware messages for Oracle Exadata Database Machine and Oracle Exadata Rack. This appendix contains the following topics:

Note:

For ease of reading, the name "Oracle Exadata Rack" is used when information refers to both Oracle Exadata Database Machine and Oracle Exadata Storage Expansion Rack.

See Also:

Oracle Database Error Messages Reference for information about Oracle Database SNMP error messages

D.1 Generic Alert Messages: HALRT-00001 to HALRT-00500

These alert messages are in the range HALRT-00001 through HALRT-00500.

HALRT-00002, Chassis Intrusion - Physical Security Violation

Cause: Detected a Physical Security Violation on the chassis.

Action: This is an informational alert and no user action is specified.

HALRT-00003, Chassis Intrusion (Physical Security Violation) Event Cleared

Cause: Detected a clear event of Physical Security Violation on the chassis.

Action: This is an informational alert and no user action is specified.

HALRT-00004, CPU Internal Error

Cause: Detected an Internal CPU error

Action: Shut down the system, and examine the CPU error.

HALRT-00005, CPU Internal Error Cleared

Cause: Detected a clear event for CPU internal error.

Action: This is an informational alert and no user action is specified.

HALRT-00006, CPU Configuration Error

Cause: Detected a CPU configuration error.

Action: Shut down the system, and examine the CPU error.

HALRT-00007, CPU Configuration Error Cleared

Cause: Detected a clear event for a CPU configuration error.

Action: This is an informational alert and no user action is specified.

HALRT-00008, CPU Presence (Processor Presence detected)

Cause: Detected presence event for a new CPU

Action: Shut down the system, and examine the CPU error.

HALRT-00009, CPU Not Present (Processor Not Present)

Cause: Detected a CPU is not present.

Action: This is an informational alert and no user action is specified.

HALRT-00010, System Event Log (SEL) Full (Logging Disabled)

Cause: System event log detected to be full.

Action: This is an informational alert and no user action is specified.

HALRT-00011, ASR (Automatic System Recovery) Timer Expired

Cause: Automatic System Recovery timer expired.

Action: This is an informational alert and no user action is specified.

HALRT-00012, ASR (Automatic System Recovery) Reset Occurred

Cause: Automatic System Recovery reset occurred.

Action: This is an informational alert and no user action is specified.

HALRT-00013, ASR (Automatic System Recovery) Power Down Occurred

Cause: Automatic System Recovery was powered down.

Action: This is an informational alert and no user action is specified.

HALRT-00014, ASR (Automatic System Recovery) Power Cycle Occurred

Cause: Automatic System Recovery power was cycled.

Action: This is an informational alert and no user action is specified.

HALRT-00015, {0} Sensor Threshold state change: Sensor Component Name: {1} Sensor State: {2} Sensor Threshold Type: {3} Sensor Threshold Severity: {4} Sensor Value: {5} Sensor Threshold Value: {6} Sensor Additional Info: {7}

Cause: The sensor threshold state has changed.

Action: Examine the sensor state change or error. If it is unexpected and has not been cleared yet, contact Oracle Support Services.

HALRT-00016, A {0} component is suspected of causing a fault. Component Name: {1} Fault class: {2} Fault certainity: {3} Fault message: {4} Trap Additional Info: {5}
Level

Critical

Cause: A component may have caused a fault to occur.

Action: Refer to the additional information in the alert message.

HALRT-00017, A {0} component fault has been cleared. Component Name: {1} Trap Additional Info: {2}
Level

Clear

Cause: The component fault has cleared.

Action: This is an informational alert and no user action is specified.

HALRT-00018, A {0} sensor has detected an error. Component Name: {1} Trap Additional Info: {2}

Cause: An error was detected by a sensor.

Action: Examine the sensor state change or error. If it is unexpected and has not been cleared yet, contact Oracle Support Services.

HALRT-00019, A {0} sensor has returned to its normal state. Component Name: {1} Trap Additional Info: {2}

Cause: The sensor has returned to its normal state.

Action: This is an informational alert and no user action is specified.

HALRT-00020, A field replaceable unit at {0} has been inserted into the system.

Cause: A unit was inserted into the system.

Action: This is an informational alert and no user action is specified.

HALRT-00021, A field replaceable unit at {0} has been removed from the system.

Cause: A unit was removed from the system.

Action: This is an informational alert and no user action is specified.

HALRT-00022, The component operational state has changed or is changing to disabled. Component Name: {0} Disable Reason: {1} Trap Additional Info: {2}

Cause: The operational state for a component has changed.

Action: This is an informational alert and no user action is specified.

HALRT-00023, The component operational state has changed or is changing to enabled. Component Name: {0} Trap Additional Info: {1}

Cause: The operational state for a component has changed.

Action: This is an informational alert and no user action is specified.

HALRT-00024, An error has been detected in the period before the operating system has taken control of the system.

Cause: An error was detected.

Action: Capture any error message on the console. Restart or power cycle the system and try to bring it back to operation. Contact Oracle Support Services with the error messages.

HALRT-00025, The high availability component identified by {0} has changed state. Old HA State: {1} New HA State: {2} Trap Additional Info: {3}

Cause: The state for a high availability component has changed.

Action: Refer to the additional information in the alert message.

HALRT-00026, An intrusion sensor has detected that someone may have physically tampered with the system.

Cause: A sensor has detected a change to the system.

Action: This is an informational alert and no user action is specified.

HALRT-00027, The hard drive has changed state. Component Name: {0} New State: {1}

Cause: The state of the hard drive has changed.

Action: This is an informational alert and no user action is specified.

HALRT-00028, This is a test trap.

Cause: User generated a test trap, and an alert was created.

Action: This is an informational alert and no user action is specified.

HALRT-00030, A {0} component fault has been cleared.

Cause: A component fault was cleared.

Action: This is an informational message, and no action is required.

D.2 Temperature Alert Messages: HALRT-00513 to HALRT-00600

These alert messages are in the range HALRT-00513 through HALRT-00600.

HALRT-00513, Under-Temperature Warning (Lower non-critical, going low).

Cause: The temperature was below specified limit.

Action: Examine the thermal degradation. Shut down the system and move data out of this cell.

HALRT-00514, Under-Temperature Warning Cleared.

Cause: The low temperature warning was cleared.

Action: This is an informational alert and no user action is specified.

HALRT-00515, Under-Temperature Problem (Lower Critical - going low).

Cause: A low temperature problem was detected.

Action: Shut down the system. Determine cause of the thermal failure. If necessary, move data out of this cell.

HALRT-00516, Under-Temperature Problem Cleared.

Cause: The low temperature problem was cleared.

Action: This is an informational alert and no user action is specified.

HALRT-00517, Over-Temperature warning (Upper non-critical, going high).

Cause: The temperature was above the limit.

Action: Examine the thermal degradation. Shut down the system and move data out of this cell.

HALRT-00518, Over-Temperature warning Cleared.

Cause: The high temperature warning was cleared.

Action: This is an informational alert and no user action is specified.

HALRT-00519, Over-Temperature Problem (Upper Critical - going high).

Cause: A high temperature was detected.

Action: Shut down the system. Determine cause of the thermal failure. If necessary, move data out of this cell.

HALRT-00520, Over-Temperature Problem Cleared.

Cause: The high temperature problem was cleared.

Action: This is an informational alert and no user action is specified.

HALRT-00521, CPU Thermal Trip (Over Temperature Shutdown).

Cause: The CPU high temperature shut down was tripped.

Action: Shut down the system. Determine cause of the thermal failure. If necessary, move data out of this cell.

HALRT-00522, CPU Thermal Trip (Over Temperature Shutdown) Cleared.

Cause: The CPU high temperature shut down was cleared.

Action: This is an informational alert and no user action is specified.

D.3 Fan Alert Messages: HALRT-00616 to HALRT-00700

These alert messages are in the range HALRT-00616 through HALRT-00700.

HALRT-00616, Generic Critical Fan Failure.

Cause: A fan has failed.

Action: Shut down the system. Determine the cause of the fan failure. Replace the fan. If necessary, move data out of this cell.

HALRT-00617, Generic Critical Fan Failure Cleared.

Cause: A fan failure was cleared.

Action: This is an informational alert and no user action is specified.

HALRT-00618, Fan Redundancy Lost.

Cause: A redundant fan has stopped functioning.

Action: This is an informational alert and no user action is specified.

HALRT-00619, Fan redundancy Has Returned to Normal.

Cause: A redundant fan has started to function normally.

Action: This is an informational alert and no user action is specified.

D.4 Power Supply/Converters Alert Messages: HALRT-00717 to HALRT-00800

These alert messages are in the range HALRT-00717 through HALRT-00800.

HALRT-00717, Power Supply Redundancy Lost.

Cause: A redundant power supply has stopped functioning.

Action: This is an informational alert and no user action is specified.

HALRT-00718, Power Supply Redundancy Has Returned to Normal,

Cause: A redundant power supply has started to function normally.

Action: This is an informational alert and no user action is specified.

HALRT-00719, Power Supply Inserted.

Cause: A power supply was inserted into the system.

Action: This is an informational alert and no user action is specified.

HALRT-00720, Power Supply Removed.

Cause: A power supply was removed from the system.

Action: Examine the power supply. Replace the power supply if necessary.

HALRT-00721, Power Supply Failure.

Cause: A power supply has failed.

Action: Examine the power supply. Replace the power supply if necessary.

HALRT-00722, Power Supply Failure Cleared.

Cause: A power supply failure was cleared.

Action: This is an informational alert and no user action is specified.

HALRT-00723, Power Supply Warning.

Cause: A power supply problem has set off a warning.

Action: Examine the power supply. Replace the power supply if necessary.

HALRT-00724, Power Supply Warning Cleared.

Cause: A power supply warning was cleared.

Action: This is an informational alert and no user action is specified.

HALRT-00725, Power Supply AC Lost.

Cause: A power supply has lost AC power.

Action: Examine the power supply. Replace the power supply if necessary.

HALRT-00726, Power Supply AC Restored.

Cause: A power supply had its AC power restored.

Action: This is an informational alert and no user action is specified.

D.5 Network Alert Messages: HALRT-00912 to HALRT-01000

These alert messages are in the range HALRT-00912 through HALRT-01000.

HALRT-00912, Infiniband port {0} indicates invalid state: {1}.

Cause: InfiniBand device indicated an invalid state.

Action: Use ibstatus to check the InfiniBand configuration, and verify that both ports show state ACTIVE and the expected Gb per second. The alert is cleared when the port status is ACTIVE. One potential common cause for the InfiniBand link negotiating to a lower link rate is that the InfiniBand cable connectors on the HCA or the switch are loose. Ensuring the InfiniBand connector fits tightly in the HCA, and the switch usually solves this problem.

A port may show status DOWN after a switch reboot. The port is automatically made ACTIVE after a few minutes.

HALRT-00913, Infiniband port {0} indicates invalid rate: {1} Gps.

Cause: InfiniBand device indicated invalid rate.

Action: Use the CellCLI command LIST IBPORT DETAIL to check the port. Verify that both ports show the expected Gb per second. A common cause for the InfiniBand link negotiating to a lower link rate is that the InfiniBand cable connectors on the HCA or the switch are loose. Ensuring the InfiniBand connector fits tightly in the HCA and in the switch usually solves this problem.

HALRT-00914, Infiniband port status is OK.

Cause: InfiniBand device status was all right.

Action: This is an informational alert and no user action is specified.

HALRT-00915, Infiniband port {0} is showing non-zero error counts.

Cause: The error counts for RcvErrors and SymbolErrors on the specified port were non-zero. A non-zero error count can be caused by a bad cable, or a cable that is not properly seated, or by a bad port on the HCA or switch. Manually disabling and enabling InfiniBand ports or resetting InfiniBand switches can also lead to these errors.

Action: Use the CellCLI command LIST IBPORT DETAIL to check the port. Verify that both ports show the expected Gb per second. A common cause for the InfiniBand link negotiating to a lower link rate is that the InfiniBand cable connectors on the HCA or the switch are loose. Ensuring the InfiniBand connector fits tightly in the HCA and in the switch usually solves this problem.

D.6 Hard Disk and Flash Disk Alert Messages: HALRT-01001 to HALRT-01200

HALRT-01001: Physical drive status changed on on Bus: {0}, Status: {1}.

Cause: The status of the physical drive changed.

Action: This is an informational message.

HALRT-01002: Spare drive status changed on Bus: {0}, Status: {1}.

Cause: The status of the spare drive changed.

Action: This is an informational message.

HALRT-01003: Factory Threshold exceeded for physical drive on Bus: {0}.

Cause: A physical drive exceeded the factory threshold on the specified bus.

Action: This is an informational message.

HALRT-01004: Physical drive status changed on Controller: {0}, Bus: {1}, Bay: {2}, Status: {3}.

Cause: The status of the physical drive changed.

Action: This is an informational message.

HALRT-01005: Spare drive status changed on Controller: {0}, Bus: {1}, Bay: {2}, Status: {3}.

Cause: The status of the spare drive changed.

Action: This is an informational message.

HALRT-01006: Factory Threshold exceeded for physical drive on Controller: {0}, Bus: {1}, Bay: {2}.

Cause: The physical drive exceeded the factory threshold values.

Action: This is an informational message.

HALRT-01007: SCSI physical drive status changed. Status: {0}

Cause: The status of the SCSI physical drive changed.

Action: This is an informational message.

HALRT-01008: SCSI physical drive status changed on Drive: {0} Controller: {1}, Bus: {2}, Status: {3}.

Cause: The status of the SCSI physical drive changed.

Action: This is an informational message.

HALRT-01009: SAS physical drive status changed on Drive: {0} Location: {1}, HBA location: {2}, HBA index: {3}, Status {4}.

Cause: The status of the SAS physical drive changed.

Action: This is an informational message.

HALRT-01010: Physical drive status changed on Drive: {0} Controller: {1}, Bus: {2}, Bay: {3}, Status {4}.

Cause: The status of the physical drive changed.

Action: This is an informational message.

HALRT-01011: Spare drive status changed on Drive: {0} Controller: {1}, Bus: {2}, Bay: {3}, Status {4}.

Cause: The status of the spare drive changed.

Action: This is an informational message.

HALRT-01012: Factory Threshold exceeded for physical drive on Drive: {0} Controller: {1}, Bus: {2}, Bay: {3}.

Cause: The physical drive exceeded the factory threshold values.

Action: This is an informational message.

HALRT-01014: Fusion flash drive status changed on Drive: {0}, Status {1}.

Cause: The flash drive status changed.

Action: This is an informational message.

HALRT-01015: Physical drive inserted on Adapter: {0} Device Id: {1}, Enclosure ID: {2}, Slot ID: {3}.

Cause: The physical drive was inserted.

Action: This is an informational message.

HALRT-01016: Physical drive removed on Adapter: {0} Device ID: {1}, Enclosure ID: {2}, Slot ID: {3}.

Cause: The physical drive was removed.

Action: If the physical drive was removed unintentionally, replace it back immediately.

HALRT-01017: Physical drive state changed from {0} to {1}. Adapter: {2} Device ID: {3}, Enclosure ID: {4}, Slot ID: {5}.

Cause: The physical drive status has changed.

Action: This is an informational message.

HALRT-01018: FRU changed. Adapter: {0} Device ID: {1}, Enclosure ID: {2}, Slot ID: {3}, Enclosure ID: {4} FRU {5}.

Cause: The field replaceable unit (FRU) was changed on the adapter.

Action: This is an informational message.

HALRT-01020: Physical drive not supported. Adapter: {0} Device ID: {1}, Enclosure ID: {2}, Slot ID: {3}.

Cause: The physical drive is not supported on the adapter.

Action: If the physical drive was removed unintentionally, replace it back immediately.

HALRT-01021: Physical drive not certified. Adapter: {0} Device ID: {1}, Enclosure ID: {2}, Slot ID: {3}.

Cause: The physical drive was not certified.

Action: If the physical drive was removed unintentionally, replace it back immediately.

HALRT-01023: This is a system disk. It is extremely important to replace this disk soon. If the other system disk on this cell fails before this disk is replaced and synced, the cell along with all data on it will go offline.

Level: Warning

Cause: The system disk needs to be replaced.

Action: Replace the system disk as soon as possible.

HALRT-01024: Physical {0} disk error count is increasing. Disk {1}, Serial Number: {2}, Slot Number: {3}

Level: Critical

Cause: The disk error count increased since the last disk check.

Action: Monitor the physical disk errors and replace if necessary.

HALRT-01025: Physical {0} disk error count is stable. Disk: {1}, Serial Number: {2}, Slot Number: {3}.

Level: Clear

Cause: The disk error count did not increase since the last disk check.

Action: This is an informational message.

HALRT-01027: Flash celldisk {0} write performance is degraded. The supercap module on the Flash card may have failed. Flash disk name : {1} Disk serial number: {2} Slot number: {3}

Cause: The write performance for the flash cell disk was degraded.

Action: This flash disk, flash PCI card or Energy Storage Module (ESM) should be replaced. If all disks on the PCI card show degraded performance, then check the ESM LED on the PCI card which is visible from the back of the cell chassis. If this LED is amber, then the ESM should be replaced. If the disks being replaced have persistent data, then rebalance the data out of these disks. Next, replace the flash disk. If there was persistent data on flash disks, then rebalance data back into the disks. The flash cache portion provided by this flash disk will be automatically disabled.

HALRT-01028: Flash celldisk {0} write performance problem has been resolved.

Cause: The performance problem for the flash cell disk was resolved.

Action: This is an informational message.

HALRT-01029: {0} {1} is rejected because firmware upgrade failed.

Level: Critical

Cause: The firmware upgrade for the physical disk failed.

Action: Upgrade the firmware on the disk manually. Restart MS to auto-online the disk.

HALRT-01030: {0} {1} is rejected because the logical block addressing format is wrong.

Level: Critical

Cause: The physical disk has wrong logical block addressing format.

Action: Format the disk manually using the following command:
nvmecli --format --device={0} --type={1}
Then run ALTER PHYSICALDISK REENABLE FORCE to online the disk. This action will erase all data on the disk.
HALRT-01031: Failed to power off the {0} in slot {1}. Status: {2}, Manufacturer: {3}, Model Number: {4}, Size: {5}, Serial Number: {6}, Firmware: {7}

Level: Warning

Cause: Failed to power off the disk in slot {1}.

Action: The disk cannot be safely replaced online. Contact Oracle Support Services.

HALRT-01035: {0} {1} firmware could not be upgraded. Inserted disks will be accepted because MS_ACCEPT_DISKFW_DIFFERENT is set to true.

Level: Informational

Cause: The firmware upgrade failed.

Action: This is an informational message.

HALRT-01036: Oracle Exadata discovered the following problems in the device utilities: {0}.

Cause: A problem has been discovered. The problem is one of the following:

  • HALRT-01037: {0} output has duplicate name: {1}

  • HALRT-01038: {0} output has duplicate serial number: {1}.

  • HALRT-01038: {0} output has duplicate serial number: {1}.

  • HALRT-01040: Cannot find device name for the disk with target ID: {0}

Action: The device monitoring utilities had unexpected outputs. A resolved alert will be sent when the problem is resolved. If the problem persists, then contact Oracle Support Services.

HALRT-01041: The problems in the device utilities have been resolved.

Level: Clear

Cause: The problem was resolved.

Action: This is an informational message.

HALRT-01042: {0} was replaced. Status: {1} Manufacturer : {2} Model Number : {3} Size: {4} Serial Number : {5} Firmware: {6} Slot Number : {7} Cell Disk: {9} Grid Disk: {10}.

Level: Warning

Cause: A disk of size {4} in slot {7} was replaced.

Action: The grid disks and cell disk are automatically re-created on the new physical disk. If the grid disks were part of an Oracle ASM disk group, then they will be added back to the disk group, and the data will be rebalanced.

HALRT-01043: {0} was replaced. Status: {1} Manufacturer : {2} Model Number : {3} Size: {4} Serial Number : {5} Firmware: {6} Slot Number : {7} Cell Disc: {9} Grid Disk: {10} Flash Cache: {11} Flash Log {12}.

Level: Warning

Cause: The flash disk of size {4} in slot {7} was replaced.

Action:

  • If the flash disk in this slot was previously used for flash cache, then flash cache will be automatically re-enabled.

  • If the flash disk in this slot was previously used for flash log, then flash log will be automatically re-enabled.

  • If the flash disk in this slot was previously used for grid disks, then grid disks will be automatically recreated and data will be automatically rebalanced by Oracle ASM.

HALRT-01044: {0} failed. Status: {1} Manufacturer : {2} Model Number : {3} Size: {4} Serial Number : {5} Firmware: {6} Slot Number : {7} Cell Disk: {9} Grid Disk: {10}.

Level: Critical

Cause: A system disk failed.

Action: The system hard disk has failed. A white Locator LED has been lit to help locate the affected cell, and an amber Fault-Service Required LED and a blue OK to Remove LED have both been lit on the drive to help locate the affected drive. Please replace the drive.

Oracle ASM rebalance will automatically restore the data redundancy.

HALRT-01045: {0} entered predictive failure status. Status: {1} Manufacturer : {2} Model Number : {3} Size: {4} Serial Number : {5} Firmware: {6} Slot Number : {7} Cell Disk: {8} Grid Disk: {9}.

Level: Critical

Cause: The system hard disk entered predictive failure status.

Action: Informational. The system hard disk has entered predictive failure status. A white Locator LED has been turned on to help locate the affected cell, and an amber Fault-Service Required LED has been lit on the drive to help locate the affected drive.

The data from the disk is automatically rebalanced by Oracle ASM to other disks. Another alert will be sent and a blue OK to Remove LED will be lit on the drive when rebalance completes. Wait until the rebalance has completed before replacing the disk.

HALRT-01046: {0} failed. Status: {1} Manufacturer : {2} Model Number : {3} Size: {4} Serial Number : {5} Firmware: {6} Slot Number : {7} Cell Disk: {8} Grid Disk: {9}.

Level: Critical

Cause: The hard disk failed.

Action: The data hard disk has failed. A white Locator LED has been lit to help locate the affected cell, and an amber Fault-Service Required LED and a blue OK to Remove LED have both been lit on the drive to help locate the affected drive. Please replace the drive.

Oracle ASM rebalance will automatically restore the data redundancy.

HALRT-01047: {0} entered predictive failure status. Status: {1} Manufacturer : {2} Model Number : {3} Size: {4} Serial Number : {5} Firmware: {6} Slot Number : {7} Cell Disk: {8} Grid Disk: {9}.

Level: Critical

Cause: The data hard disk entered predictive failure status.

Action:A white Locator LED has been turned on to help locate the affected cell, and an amber Fault-Service Required LED has been lit on the drive to help locate the affected drive.

The data from the disk will be automatically rebalanced by Oracle ASM to other disks. Another alert will be sent and a blue OK to Remove LED will be lit on the drive when rebalance completes. Please wait until rebalance has completed before replacing the disk.

HALRT-01048: {0} failed. Status: {1} Manufacturer : {2} Model Number : {3} Size: {4} Serial Number : {5} Firmware: {6} Slot Number : {7} Cell Disk: {8} Grid Disk: {9}.

Level: Critical

Cause: The flash disk failed.

Action: A white Locator LED has been lit to help locate the affected cell. Please replace the flash disk.

If the flash disk is used for flash cache, then flash cache will be disabled on this disk thus reducing the effective flash cache size. If the flash disk is used for flash log, then flash log will be disabled on this disk thus reducing the effective flash log size. If the flash disk is used for grid disks, then Oracle ASM rebalance will automatically restore the data redundancy.

HALRT-01049: {0} failed. Status: {1} Manufacturer : {2} Model Number : {3} Size: {4} Serial Number : {5} Firmware: {6} Slot Number : {7} Cell Disk: {8} Grid Disk: {9}.

Level: Critical

Cause: The system hard disk failed.

Action: A cell Locator LED has been lit to help locate the affected cell, and an error LED has been lit on the drive to help locate the affected drive. Please replace the drive.

Oracle ASM rebalance will automatically restore the data redundancy.

HALRT-01050: {0} entered predictive failure status. Status: {1} Manufacturer : {2} Model Number : {3} Size: {4} Serial Number : {5} Firmware: {6} Slot Number : {7} Cell Disk: {8} Grid Disk: {9}.

Level: Critical

Cause: The system hard disk entered predictive failure status.

Action: Informational. The data from the disk will be automatically rebalanced by Oracle ASM to other disks. Another alert will be sent when rebalance completes. Please wait until rebalance has completed before replacing the disk.

HALRT-01051: {0} failed. Status: {1} Manufacturer : {2} Model Number : {3} Size: {4} Serial Number : {5} Firmware: {6} Slot Number : {7} Cell Disk: {8} Grid Disk: {9}.

Level: Critical

Cause: The data hard disk failed.

Action: A cell Locator LED has been lit to help locate the affected cell, and an error LED has been lit on the disk to help locate the affected disk. Please replace the drive.

Oracle ASM rebalance will automatically restore the data redundancy.

HALRT-01052: {0} entered predictive failure status. Status: {1} Manufacturer : {2} Model Number : {3} Size: {4} Serial Number : {5} Firmware: {6} Slot Number : {7} Cell Disk: {8} Grid Disk: {9}.

Level: Critical

Cause: The data hard disk entered predictive failure status.

Action: Informational. The data from the disk will be automatically rebalanced by Oracle ASM to other disks. Another alert will be sent when rebalance completes. Please wait until rebalance has completed before replacing the disk.

HALRT-01053: The Oracle ASM drop operation on the following disk failed due to ORA-{0} ASM Disk Name: {1} ASM Diskgroup: {2} Grid Disk: {3} Cell Disk: {4} Physical Disk: {5} Physical Disk Status: {6}.

Level: Warning

Cause: The grid disk was not dropped from the Oracle ASM disk group because of the specified reason.

Action: Informational. Oracle Exadata System Software continues to retry the DROP operation, and an alert is sent when the command succeeds.

HALRT-01054: The Oracle ASM drop operation on the following disk failed due to ORA-{0} ASM Disk Name: {1} ASM Diskgroup: {2} Grid Disk: {3} Cell Disk: {4} Physical Disk: {5} Physical Disk Status: {6}.

Level: Warning

Cause: The Oracle ASM DROP command failed because of the specified reason.

Action: After the error is resolved, retry the DROP command manually on the Oracle ASM disk.

HALRT-01055: The Oracle ASM rebalance operation on the following disk failed due to ORA-{0} ASM Disk Name: {1} ASM Diskgroup: {2} Grid Disk: {3} Cell Disk: {4} Physical Disk: {5} Physical Disk Status: {6}.

Level: Warning

Cause: The Oracle ASM rebalance operation failed because of the specified reason.

Action: This is an informational message.

HALRT-01056: The Oracle ASM rebalance operation on the following disk resumed. ASM Disk Name: {0} ASM Diskgroup: {1} Grid Disk: {2} Cell Disk: {3} Physical Disk: {4} Physical Disk Status: {5}.

Level: Warning

Cause: The Oracle ASM rebalance operation resumed.

Action: This is an informational message.

HALRT-01057: The Oracle ASM add operation on the following disk failed due to ORA-{0} ASM Disk Name: {1} ASM Diskgroup: {2} Grid Disk: {3} Cell Disk: {4} Physical Disk: {5} Physical Disk Status: {6}.

Level: Warning

Cause: The Oracle ASM operation to add the disk failed because of the specified reason.

Action: Informational. Oracle Exadata System Software continues to retry the command, and an alert is sent when the command succeeds.

HALRT-01058: The Oracle ASM add operation on the following disk failed due to ORA-{0} ASM Disk Name: {1} ASM Diskgroup: {2} Grid Disk: {3} Cell Disk: {4} Physical Disk Name: {5} Physical Disk Status: {6}.

Level: Warning

Cause: The Oracle ASM operation to add the disk failed because of the specified reason.

Action: After the error is resolved, manually retry the command to add the Oracle ASM disk.

HALRT-01059: Oracle Exadata completed the rebalance operation triggered by adding the following ASM disks: ASM Disk Names: {0} ASM Diskgroups: {1} Grid Disks: {2} Cell Disk: {3} Physical Disk: {4} Physical Disk Status : {5}.

Level: Clear

Cause: The rebalance operation to add grid disks to Oracle ASM disk groups completed.

Action: This is an informational message.

HALRT-01060: Oracle Exadata completed the rebalance operation triggered by dropping the following ASM disks: ASM Disk Names: {0} ASM Diskgroups: {1} Grid Disks: {2} Cell Disk: {3} Physical Disk: {4} Physical Disk Status : {5}.

Level: Warning

Cause: The rebalance operation to drop the grid disks from the Oracle ASM disk groups completed.

Action: This is an informational message.

HALRT-01061: {0} is ready to use. Status: {1} Manufacturer: {2} Model Number: {3} Size: {4} Serial Number: {5} Firmware: {6} Slot Number: {7} Cell Disk: {8} Grid Disk: {9} Flash Cache: {10} Flash Log: {11}.

Level: Clear

Cause: The disk is ready for use.

Action: This is an informational message.

HALRT-01062: {0} is ready to use. Status: {1} Manufacturer: {2} Model Number: {3} Size: {4} Serial Number: {5} Firmware: {6} Slot Number: {7} Cell Disk: {8} Grid Disk: {9}.

Level: Clear

Cause: The disk is ready to use.

Action: This is an informational message.

HALRT-01063: The Oracle ASM rebalance operation on the following disk failed as ASM rebalance power limit is 0. ASM Disk Name: {0} ASM Diskgroup: {1} Grid Disk: {2} Cell Disk: {3} Physical Disk: {4} Physical Disk Status : {5}.

Level: Warning

Cause: The rebalance operation failed because the Oracle ASM rebalance operation is disabled.

Action: Examine and change the ASM_POWER_LIMIT initialization parameter to a non-zero value.

HALRT-01064: Oracle Exadata completed the rebalance operation triggered by adding the following ASM disks: ASM Disk Names: {0} ASM Diskgroups: {1} Grid Disks: {2} Cell Disk: {3} Physical Disk: {4} Physical Disk Status : {5}.

Level: Warning

Cause: The rebalance operation to add grid disks to Oracle ASM disk groups completed.

Action: This is an informational message.

HALRT-01065: {0} output has duplicate slot numbers: {1}

Level:

Cause:

Action:

HALRT-01067: {0} failed. Status: {1} Manufacturer: {2} Model Number: {3} Size: {4} Serial Number: {5} Firmware: {6} Slot Number: {7}

Level: Critical

Cause: The system M.2 disk failed.

Action: Replace the disk.

Detailed information on this problem can be found in My Oracle Support Doc ID 2285530.1.

HALRT-01068: {0} entered predictive failure status. Status: {1} Manufacturer: {2} Model Number: {3} Size: {4} Serial Number: {5} Firmware: {6} Slot Number: {7}

Level: Critical

Cause: The system M.2 disk entered predictive failure status.

Action: Replace the disk.

Detailed information on this problem can be found in My Oracle Support Doc ID 2285530.1.

HALRT-01069: {0} was replaced. Status: {1} Manufacturer: {2} Model Number: {3} Size: {4} Serial Number: {5} Firmware: {6} Slot Number: {7}

Level: Informational

Cause: The system M.2 disk was replaced.

Action: This is an informational alert.

HALRT-01070: Previously missing {0} is found. Status: {1} Manufacturer: {2} Model Number: {3} Size: {4} Serial Number: {5} Firmware: {6} Slot Number: {7}

Level: Informational

Cause: A previously missing disk is now available.

Action: This is an informational alert.

HALRT-01071: {0} status changed to normal. Status: {1} Manufacturer: {2} Model Number: {3} Size: {4} Serial Number: {5} Firmware: {6} Slot Number: {7}

Level: Informational

Cause: The status of the disk changed to normal.

Action: This is an informational alert.

HALRT-01101: Logical drive status changed. Bus: {0}, Status: {1}

Cause: The status of the logical drive changed.

Action: This is an informational alert.

HALRT-01101: Logical drive status changed. Bus: {0}, Status: {1}

Cause: The status of the logical drive changed.

Action: This is an informational alert.

HALRT-01102: Logical drive status changed. Drive number: {0}, Controller location: {1}, Controller Index: {2}, Status: {3}, Cell Disk: {4}

Cause: The status of the logical drive changed.

Action: This is an informational alert.

HALRT-01103: SCSI logical drive status changed. Status: {0}

Cause: The status of the SCSI logical drive changed.

Action: This is an informational alert.

HALRT-01104: SCSI logical drive status changed. Drive: {0}, Osname: {1}, Controller: {2}, Bus: {3}, Status: {4}, Cell Disk: {5}

Cause: The status of the SCSI logical drive changed.

Action: This is an informational alert.

HALRT-01105: SAS logical drive status changed. Drive: {0}, Osname: {1}, HBA location: {2}, HBA index: {3}, Status: {4}, Cell Disk: {5}

Cause: The status of the SAS logical drive changed.

Action: This is an informational alert.

HALRT-01107: Disk drive {0} is in WriteThrough caching mode. Write Performance on this drive will be affected. Please contact Oracle Support.

Cause: The drive was placed in WriteThrough caching mode.

Action: Contact Oracle Support to determine why the drive is in WriteThrough cache mode. Correct any problems found. Change the disk to use WriteBack cache mode to improve performance.

HALRT-01108: Logical drive status changed. LUN: {0}. Status: {1}. Physical {2} : {3}. Slot Number: {4}. Serial Number: {5}. Cell Disk: {6}. Grid Disks: {7}.

Cause: The status of the logical drive has changed.

Action: This is an informational alert.

HALRT-01109: Disk controller battery temperature exceeded the threshold of {0} Celsius. All disk drives have been placed in WriteThrough caching mode. The flash drives are not affected. Battery Serial Number: {1} Battery Type: {2} Battery Temperature: {3} Full Charge Capacity: {4} Relative Charge {5} Ambient Temperature: {6}.

Cause: Temperature exceeded the threshold.

Action: Check if the ambient temperature is below 32 Celsius and if the fans are working.

HALRT-01110: Logical drive found. It was empty. Failed creating cell disk and grid disks on it. LUN: {0}. Status: {1}. Physical {2} disk: {3}. Slot Number: {4}. Serial Number: {5}.

Cause: The logical drive was found.

Action: This is an informational alert.

HALRT-01111: Could not sync the following change in disk state with Cellsrv.

Cause:

Action: This is an informational alert.

HALRT-01112: Found LUNs : {0}.

Cause:

Action: This is an informational alert.

HALRT-01113: Lost LUNs : {0}.

Cause:

Action: This is an informational alert.

HALRT-01114: Need to resync LUNs : {0}.

Cause:

Action: This is an informational alert.

HALRT-01115: BGI completed with uncorrectable errors on Adapter {0} VD Target {1}.

Cause: BGI completed with errors.

Action: This is an informational alert.

HALRT-01116: BGI failed on Adapter {0} VD Target {1}.

Cause: BGI failed on adapter.

Action: The LUN on this virtual drive has failed. Drop the LUN and re-create it.

HALRT-01117: VD state changed on Adapter {0} VD Target {1} from {2} to {3}.

Cause: The LUN state was changed.

Action: This is an informational alert.

HALRT-01118: VD bad block table cleared on Adapter {0} VD Target {1}.

Cause: The LUN bad block table was cleared.

Action: This is an informational alert.

HALRT-01121: Not configured.

Cause:

Action: This is an informational alert.

HALRT-01123: {0} is rejected due to incorrect disk model. Status: {1} Manufacturer: {2} Model Number: {3} Size: {4} Serial Number: {5} Firmware: {6} Slot Number: {7} Cell Disk: {8} Grid Disk: {9}

Level: Critical

Cause: The hard disk or LUN was rejected.

Action: Oracle Exadata Storage Server is unable to use this hard disk because the disk model is not supported. Please remove this hard disk and replace it with a supported disk. This cell supports the following disk models: {0}.

HALRT-01124: {0} was replaced. Status: {1} Manufacturer: {2} Model Number: {3} Size: {4} Serial Number: {5} Firmware: {6} Slot Number: {7} Cell Disk: {8} Grid Disk: {9}.

Level: Warning

Cause: The hard disk was replaced.

Action: This is an informational message.

HALRT-01125: {0} was removed and inserted. Status: {1} Manufacturer: {2} Model Number: {3} Size: {4} Serial Number: {5} Firmware: {6} Slot Number: {7} Flash Cache: {8} Flash Log: {9}.

Level: Informational

Cause: CELLSRV may have reported I/O errors when the physical disk was removed.

Action: Informational. If any grid disk on this physical disk went offline in Oracle ASM as a result, then Oracle ASM will automatically bring the disk online.

HALRT-01126: The full charge capacity of the disk controller battery has fallen below the minimum threshold of {0} mAh. All disk drives have been placed in WriteThrough caching mode. Disk write performance may be somewhat reduced. The flash drives are not affected. Battery Serial Number: {1} Battery Type: {2} Battery Temperature: {3} Full Charge Capacity: {4} Relative Charge: {5} Ambient Temperature: {6}.

Cause: The full charge capacity of the battery was below the threshold.

Action: Replace disk controller battery.

HALRT-01127: All disk drives have been placed in WriteThrough caching mode. The flash drives are not affected. Battery Serial Number: {1} Battery Type: {2} Battery Temperature: {3} Full Charge Capacity: {4} Relative Charge: {5} Ambient Temperature: {6}.

Cause: The cause could not be determined.

Action: Contact Oracle Support Services.

HALRT-01128: Cell disk was missing and is recreated on the {0}. Status: {1} Manufacturer: {2} Model Number: {3} Size: {4} Serial Number: {5} Firmware: {6} Slot Number: {7} Cell Disk: {8} Grid Disk: {9}.

Cause: The cell disk was missing, and has been recreated on the disk.

Action: This is an informational alert.

HALRT-01130: {0} entered poor performance status. The LUN {1} changed status to {2}. CellDisk changed status to {3}. Status: {4} Manufacturer: {5} Model Number: {6} Size: {7} Serial Number: {8} Firmware: {9} Slot Number: {10} Cell Disk: {11} Grid Disk: {12} Reason for poor performance : {13}.

Level: Critical

Cause: The hard disk or flash disk status changed to poor performance.

Action: The physical disk at slot {0} demonstrates poor performance, and should be replaced. The Oracle ASM disks associated with the grid disks on this physical disk are automatically dropped with FORCE option if possible. If drop FORCE cannot succeed due to offline partners, then the grid disks are automatically dropped normally, and an Oracle ASM rebalance will relocate the data from the poor performance disk to other disks. See "Replacing a Hard Disk Due to Disk Failure" or the alert message pertaining to the disk failure.

To replace a disk due to disk problems, perform the following procedure:

  1. Wait until the Oracle ASM disks associated with the grid disks on the physical disk have been successfully dropped. To determine if the grid disks have been dropped, query the V$ASM_DISK_STAT view on the Oracle ASM instance.

  2. Replace the physical disk. The physical disk is hot-pluggable, and can be replaced when the power is on.

    The grid disks and cell disk that existed on the previous disk in the slot will be re-created on the new physical disk. If those grid disks were part of an Oracle ASM disk group, then they will be added back to the disk group and the data will be rebalanced based on disk group redundancy and the ASM_POWER_LIMIT parameter.

    Caution:

    The disks in the first two slots are system disks which store the operating system and Oracle Exadata System Software. At least one system disk must be online for the cell to remain operational. When you replace a system disk, wait until ALTER CELL VALIDATE CONFIGURATION shows no mdadm errors, which indicates the system disk resync has completed, before replacing the other system disk.
Oracle ASM rebalance occurs when dropping or adding a disk. To check the status of the rebalance, do the following:
  • The rebalance operation may have been successfully run. Check the Oracle ASM alert logs to confirm.

  • The rebalance operation may be currently running. Check the GV$ASM_OPERATION view to determine if the rebalance operation is still running.

  • The rebalance operation may have failed. Check the ERROR_CODE column in the V$ASM_OPERATION view to determine if the rebalance operation failed.

  • Rebalance operations from multiple disk groups can be done on different Oracle ASM instances in the same cluster. One Oracle ASM instance can run one rebalance operation at a time. If all Oracle ASM instances are busy, then rebalance operations will be queued.

HALRT-01131: {0} status changed to normal. Status: {1} Manufacturer: {2} Model Number: {3} Size: {4} Serial Number: {5} Firmware: {6} Slot Number: {7} Cell Disk: {8} Grid Disk: {9}

Level: Warning

Cause: The hard disk or flash disk status changed to normal.

Action: This is an informational message.

HALRT-01132: {0} was removed. Status: {1} Manufacturer: {2} Model Number: {3} Size: {4} Serial Number: {5} Firmware: {6} Slot Number: {7} Cell Disk: {8} Grid Disk: {9}.

Level: Warning

Cause: The hard or flash disk was removed.

Action: This is an informational message.

HALRT-01133: {0} status changed to offline. Status: {1} Manufacturer: {2} Model Number: {3} Size: {4} Serial Number: {5} Firmware: {6} Slot Number: {7} Cell Disk: {8} Grid Disk: {9}.

Level: Critical

Cause: The hard or flash disk status changed to offline.

Action: This is an informational message.

HALRT-01141: Flash Disk was replaced. Status: {0} Manufacturer: {1} Model Number: {2} Size: {3} Serial Number: {4} Firmware: {5} Slot Number: {6} Cell Disk: {7} Grid Disk: {8} Flash Cache: {9} Flash Log {10}.

Level: Warning

Cause: Flash disk was replaced.

Action: This is an informational message, and no action is required.

HALRT-01143: All disk drives have been placed in WriteThrough caching mode. The controller has preserved cache for a disk drive for more than five minutes. The flash drives are not affected. Battery Serial Number: {1} Battery Type: {2} Battery Temperature: {3} Full Charge Capacity: {4} Relative Charge: {5} Ambient Temperature: {6}.

Cause: The preserved cache was not turned off for more than five minutes.

Action: Contact Oracle Support Services.

HALRT-01144: Cell disk was missing and is recreated on the {0}. Status: {1} Manufacturer: {2} Model Number: {3} Size: {4} Serial Number: {5} Firmware: {6} Slot Number: {7} Cell Disk: {8} Grid Disk: {9} Flash Cache {10} Flash Log {11}.

Cause: The cell disk was missing and has been recreated on the drive.

Action: This is an informational alert and no user action is specified.

HALRT-01145: Flash Disk status changed to predictive failure. Status: {0} Manufacturer: {1} Model Number: {2} Size: {3} Serial Number: {4} Firmware: {5} Slot Number: {6} Cell Disk: {7} Grid Disk: {8} Flash Cache: {9} Flash Log: {10}.

Level: Critical

Cause: Flash disk status changed to predictive failure.

Action: The flash disk has entered predictive failure status. A white Locator LED has been lit to help locate the affected cell.

  • If the flash disk is used for flash cache, then flash cache is disabled on this disk, reducing the effective flash cache size.

  • If flash cache is in write back mode, then dirty data on this flash disk is automatically flushed to the corresponding grid disks.

  • If the flash disk is used for flash log, then flash log is disabled on this disk, reducing the effective flash log size.

  • If the flash disk is used for grid disks, then the data from the flash disk is automatically rebalanced by Oracle ASM to other flash disks.

Another alert will be sent when all data has been rebalanced and flushed from this flash disk. Please wait until rebalance and flush have completed before replacing the flash disk.

HALRT-01146: {0} entered poor performance status. The LUN {1} changed status to {2}. CellDisk changed status to {3}. Status: {4} Manufacturer: {5} Model Number: {6} Size: {7} Serial Number: {8} Firmware: {9} Slot Number: {10} Cell Disk: {11} Grid Disk: {12} Flash Cache: {13} Flash Log: {14} Reason for poor performance: {15}.

Level: Critical

Cause: Flash disk status changed to poor performance.

Action: See "Maintaining Flash Disks on Oracle Exadata Storage Servers".

HALRT-01147: {0} status changed to normal. Status: {1} Manufacturer: {2} Model Number: {3} Size: {4} Serial Number: {5} Firmware: {6} Slot Number: {7} Cell Disk: {8} Grid Disk: {9} Flash Cache: {10} Flash Log: {11}.

Level: Warning

Cause: Flash disk status changed to normal.

Action: This is an informational message, and no action is required.

HALRT-01148: Flash Disk removed. Status: {0} Manufacturer: {1} Model Number: {2} Size: {3} Serial Number: {4} Firmware: {5} Slot Number: {6} Cell Disk: {7} Grid Disk: {8} Flash Cache: {9} Flash Log: {10}.

Level: Warning

Cause: Flash disk was removed.

Action: A flash disk has been removed or is no longer visible to Oracle Exadata Storage Server.

  • If a flash disk has just been replaced, then this alert is informational only and a flash disk replaced CLEAR alert is sent. No action is needed.

  • If flash is being used as a cache, then the only effect is that the flash cache size has been reduced on this cell. The flash disk removal does not cause an outage, data loss, or Oracle ASM rebalance.

Each flash card contains four flash disks. If all four flash disks on a card alert, then the removal is likely for a card. To see whether the flash disks are on the same card, check for identical PCI Slot numbers in the alert outputs.

HALRT-01149: {0} status changed to offline. Status: {1} Manufacturer: {2} Model Number: {3} Size: {4} Serial Number: {5} Firmware: {6} Slot Number: {7} Cell Disk: {8} Grid Disk: {9} Flash Cache: {10} Flash Log: {11}.

Level: Critical

Cause: Flash disk status changed to offline.

Action: This is an informational message, and no action is required.

HALRT-01150: Cell disk was missing and is recreated on the {0}.

Cause: The cell disk was missing, and has been recreated on the disk.

Action: This is an informational alert and no user action is specified.

HALRT-01153: Disk drive {0} is back in WriteBack caching mode.

Cause: The disk drive entered write back caching mode.

Action: This is an informational alert and no user action is specified.

HALRT-01154: Oracle Exadata Storage Server failed to auto-create cell disk and grid disks on the newly inserted physical disk. Physical Disk: {0} Status: {1} Manufacturer: {2} Model Number: {3} Size: {4} Serial Number: {5} Firmware: {6} Slot Number: {7}.

Level: Warning

Cause: The server did not auto-create the cell disk or grid disks.

Action: Oracle Exadata System Software continues to retry, and an alert is sent when the auto-creation succeeds.

HALRT-01155: All disk drives have been temporarily placed in WriteThrough caching mode because the disk controller battery was replaced. The flash drives are not affected. Battery Serial Number: {0} Battery Type: {1} Battery Temperature: {2} Full Charge Capacity: {3} Relative Charge: {4} Ambient Temperature {5}.

Cause: Disk controller battery was replaced.

Action: This is an informational message, and no action is required.

HALRT-01156: Previously missing {0} is found. Status: {1} Manufacturer: {2} Model Number: {3} Size: {4} Serial Number: {5} Firmware: {6} Slot Number: {7} Cell Disk: {8} Grid Disk: {9} Flash Cache: {10} Flash Log: {11}.

Level: Clear

Cause: The missing flash disk was found.

Action: This is an informational message, and no action is required.

  • If the flash disk in this slot was previously used for flash cache, then flash cache is automatically re-enabled.

  • If the flash disk in this slot was previously used for flash log, then flash log is automatically re-enabled.

  • If the flash disk in this slot was previously used for grid disks, then the grid disks are automatically recreated and data is automatically rebalanced by Oracle ASM.

HALRT-01157: Previously missing {0} is found. Status: {1} Manufacturer: {2} Model Number: {3} Size: {4} Serial Number: {5} Firmware: {6} Slot Number: {7} Cell Disk: {8} Grid Disk: {9}

Level: Clear

Cause: The missing hard disk was found.

Action: This is an informational message, and no action is required.

HALRT-01159: {0} import failed. Status: {1} Manufacturer: {2} Model Number: {3} Size: {4} Serial Number: {5} Firmware: {6} Slot Number: {7} .

Level: Warning

Cause: The import procedure failed for the hard disk.

Action: The system failed to import this hard disk because preserved cache exists for other missing hard disks. Reseat or replace the hard disks in {0}. Another alert is sent when all disks are successfully imported.

HALRT-01160: Failed to create LUN on {0}. Status: {1} Manufacturer: {2} Model Number: {3} Size: {4} Serial Number: {5} Firmware: {6} Slot Number: {7}

Level: Warning

Cause: The disk controller did not create a LUN on the physical disk.

Action: Contact Oracle Support Services.

HALRT-01161: All disk drives are back in WriteBack caching mode. Preserved cache has turned off. Battery Serial Number: {0} Battery Type: {1} Battery Temperature: {2} Full Charge Capacity: {3} Relative Charge: {4} Ambient Temperature: {5}.

Cause: Disk drives returned to write back caching mode.

Action: This is an informational message, and no action is required.

HALRT-01162: All disk drives are in WriteBack caching mode. Battery Serial Number: {0} Battery Type: {1} Battery Temperature: {2} Full Charge Capacity: {3} Relative Charge: {4} Ambient Temperature: {5}.

Cause: Disk drives are in write back caching mode.

Action: This is an informational message, and no action is required.

HALRT-01163: All disk drives are back in WriteBack caching mode. Battery has completed charging. Battery Serial Number: {0} Battery Type: {1} Battery Temperature: {2} Full Charge Capacity: {3} Relative Charge: {4} Ambient Temperature: {5}.

Cause: Battery completed charging, and all disk drives returned to write back caching mode.

Action: This is an informational message, and no action is required.

HALRT-01164: All disk drives are in WriteBack caching mode. Battery Serial Number: {0} Battery Type: {1} Battery Temperature: {2} Full Charge Capacity: {3} Relative Charge: {4} Ambient Temperature: {5}.

Cause: Disk drives are in write back caching mode.

Action: This is an informational message, and no action is required.

HALRT-01165: {0} can be replaced now. Status: {1} Manufacturer: {2} Model Number: {3} Size: {4} Serial Number: {5} Firmware: {6} Slot Number: {7} Cell Disk: {8} Grid Disk: {9}.

Level: Warning

Cause: Physical disk needs replacement.

Action: The data on this disk has been successfully rebalanced by Oracle ASM to other disks. A blue OK to Remove LED has been lit on the drive. Please replace the drive.

HALRT-01166: {0} can be replaced now. Status: {1} Manufacturer: {2} Model Number: {3} Size: {4} Serial Number: {5} Firmware: {6} Slot Number: {7} Cell Disk: {8} Grid Disk {9} Flash Cache {10} Flash Log {11}.

Level: Warning

Cause: Flash disk needs replacement.

Action: The data on this flash disk has been successfully rebalanced or flushed. Please replace the drive.

HALRT-01167: {0} can be replaced now. Status: {1} Manufacturer: {2} Model Number: {3} Size: {4} Serial Number: {5} Firmware: {6} Slot Number: {7} Cell Disk: {8} Grid Disk {9} Flash Cache {10} Flash Log {11} Board Tracer Number {12}

Level: Warning

Cause: The flash disk needs replacement.

Action: The data on this flash disk has been successfully rebalanced or flushed. Please replace the drive.

HALRT-01168: {0} was removed and inserted. Status: {1} Manufacturer: {2} Model Number: {3} Size: {4} Serial Number: {5} Firmware: {6} Slot Number: {7}

Level: Informational

Cause: The component was inserted.

Action: This is an informational message, and no action is required. CELLSRV may have reported I/O errors when the physical disk was removed. If any grid disk on this physical disk went offline in Oracle ASM as a result, then Oracle ASM automatically brings the disk online.

HALRT-01169: {0} entered write-through caching mode. Status: {1} Manufacturer: {2} Model Number: {3} Size: {4} Serial Number: {5} Firmware: {6} Slot Number: {7} Cell Disk: {8} Grid Disk: {9} Flash Cache {10} Flash Log {11}.

Level: Critical

Cause: The flash disk has failed.

Action: A white Locator LED has been lit to help locate the affected cell. Please replace the flash disk.

  • If the flash disk is used for flash cache, then flash cache will be disabled on this disk thus reducing the effective flash cache size.

  • If the flash disk is used for flash log, then flash log will be disabled on this disk thus reducing the effective flash log size.

  • If the flash disk is used for grid disks, then Oracle ASM rebalance will automatically restore the data redundancy.

HALRT-01170: Failed to flush the write back flash cache. Status: {0} Manufacturer: {1} Model Number: {2} Size: {3} Serial Number: {4} Firmware: {5} Slot Number: {6} Cell Disk: {7} Grid Disk: {8} Flash Cache {9} Flash Log {10}.

Level: Critical

Cause: Failed to flush the flash cache.

Action: Check the alert log for additional details. After the underlying problem is resolved, flush of the write back flash cache on this cell disk is automatically resumed.

HALRT-01171: {0} entered confinement offline status. The LUN {1} changed status to {2}. CellDisk changed status to {3}. All subsequent I/Os on this disk are failed immediately. Confinement tests will be run on the disk to determine if the disk should be dropped. Status: {4} Manufacturer: {5} Model Number: {6} Size: {7} Serial Number: {8} Firmware: {9} Slot Number: {10} Cell Disk: {11} Grid Disk: {12} Reason for confinement: {13}.

Cause: The hard disk was performing poorly, and entered confinement.

Action: If the hard disk was used for grid disks, then the Oracle ASM disks associated with the grid disks on this hard disk are offlined. Confinement tests run on this disk, and either move the disk permanently to poor performance or return the disk back to normal state.

HALRT-01172: {0} entered confinement offline status. The LUN {1} changed status to {15}. CellDisk changed status to {2}. All subsequent I/Os on this disk are failed immediately. Confinement tests will be run on the disk to determine if the disk should be dropped. Status: {4} Manufacturer: {5} Model Number: {6} Size: {7} Serial Number: {8} Firmware: {9} Slot Number: {10} Cell Disk: {11} Grid Disk: {12} Flash Cache: {13} Flash Log: {14} Reason for confinement: {15}.

Cause: The flash disk was performing poorly, and entered confinement.

Action: One of the following actions is performed:

  • If the flash disk was used for writethrough flash cache, then flash cache on this disk will be disabled causing a reduction in the effective flash cache size.

  • If the flash disk was used for writeback flash cache, then flash cache on this disk will be disabled, and read I/O to dirty data in the flash cache will go to the mirror disks on different cells. Write I/Os will go directly to the grid disks on this cell.

  • If the flash disk was used for flash log, then flash log is disabled on this disk causing a reduction of the effective flash log size.

  • If the flash disk was used for grid disks, then the Oracle ASM disks associated with the grid disks on this flash disk are offlined.

Confinement tests run on this disk, and either move the disk permanently to poor performance or return the disk back to normal state.

HALRT-01173: {0} entered confinement status. The LUN {1} changed status to {2}. CellDisk changed status to {3}. Status: {4} Manufacturer: {5} Model Number: {6} Size: {7} Serial Number: {8} Firmware: {9} Slot Number: {10} Cell Disk: {11} Grid Disk: {12} Reason for confinement: {13}.

Cause: The system disk entered confinement.

Action: Contact Oracle Support Services.

HALRT-01174: {0} entered confinement status. The LUN {1} changed status to {2}. CellDisk changed status to {3}. Status: {4} Manufacturer: {5} Model Number: {6} Size: {7} Serial Number: {8} Firmware: {9} Slot Number: {10} Cell Disk: {11} Grid Disk: {12} Flash Cache: {13} Flash Log: {14} Reason for confinement: {15}.

Cause: The disk entered confinement.

Action: Insert the disk into the correct slot.

HALRT-01175: Partition table is missing in system slot {0}.

Level: Warning

Cause: The partition table was not on the drive in the system slot.

Action: Contact Oracle Support Services.

HALRT-01176: The data disk from slot {1} was inserted into system slot {2} of the same Oracle Exadata storage server. Status: {3} Manufacturer: {4} Model Number: {5} Size: {6} Serial Number: {7} Firmware: {8} Slot Number: {9}

Level: Warning

Cause: The data disk was inserted into the wrong slot.

Action: Insert the disk into the correct slot.

HALRT-01177: The system disk from slot {0} was inserted into data slot {1} of the same Oracle Exadata storage server. Status: {2} Manufacturer: {3} Model Number: {4} Size: {5} Serial Number: {6} Firmware: {7} Slot Number: {8}.

Level: Warning

Cause: A system disk from the same Exadata Storage Server was inserted in a data disk slot.

Action: Insert the correct disk into the slot.

HALRT-01178: The system disk from a different Oracle Exadata storage server was inserted in slot {0}. Status: {1} Manufacturer: {2} Model Number: {3} Size: {4} Serial Number: {5} Firmware: {6} Slot Number: {7}.

Level: Warning

Cause: A system disk from a different Exadata Storage Server was inserted in the slot.

Action: Insert the correct disk into the slot.

HALRT-01179: A data disk from a different Oracle Exadata storage server was inserted in system slot {0}. Status: {1} Manufacturer: {2} Model Number: {3} Size: {4} Serial Number: {5} Firmware: {6} Slot Number: {7}.

Level: Warning

Cause: A data disk from a different Exadata Storage Server was inserted in a system disk slot.

Action: Insert the correct disk into the slot.

HALRT-01181: {0} entered peer failure status. Status: {1} Manufacturer: {2} Model Number: {3} Size: {4} Serial Number: {5} Firmware: {6} Slot Number: {7} Cell Disk: {8} Grid Disk: {9} Flash Cache {10} Flash Log {11}.

Level: Critical

Cause: The flash disk entered peer failure status.

Action: The flash disk has entered predictive failure status. A white Locator LED has been lit to help locate the affected cell.

  • If the flash disk is used for flash cache, then flash cache is disabled on this disk, reducing the effective flash cache size.

  • If flash cache is in write back mode, then dirty data on this flash disk is automatically flushed to the corresponding grid disks.

  • If the flash disk is used for flash log, then flash log is disabled on this disk, reducing the effective flash log size.

  • If the flash disk is used for grid disks, then the data from the flash disk is automatically rebalanced by Oracle ASM to other flash disks.

Another alert will be sent when all data has been rebalanced and flushed from this flash disk. Wait until rebalance and flush have completed before replacing the flash disk.

HALRT01182: {0} was removed before running the ALTER PHYSICALDISK DROP FOR REPLACEMENT command. tatus: {1} Manufacturer: {2} Model Number: {3} Size: {4} Serial Number: {5} Firmware: {6} Slot Number: {7} Cell Disk: {8} Grid Disk {9}.

Level: Critical

Cause: The disk was removed before the ALTER PHYSICALDISK DROP FOR REPLACEMENT command was run.

Action: This is an informational message, and no actions is required.

HALRT01183: {0} was removed before running the ALTER PHYSICALDISK DROP FOR REPLACEMENT command and inserted. {1} Manufacturer: {2} Model Number: {3} Size: {4} Serial Number: {5} Firmware: {6} Slot Number: {7}.

Level: Informational

Cause: The disk was removed before the ALTER PHYSICALDISK DROP FOR REPLACEMENT command was run.

Action: This is an informational message, and no action is required. If an Oracle ASM grid disk were on the physical disk when the disk went offline, then Oracle ASM automatically brings the disk online.

HALRT-01184: {0} automatically failed over to a spare disk. Status: {1} Manufacturer: {2} Model Number: {3} Size: {4} Serial Number: {5} Firmware: {6} Slot Number: {7} Cell Disk: {8} Grid Disk: {9}.

Level: Critical

Cause: The cell disk failed over to the spare disk.

Action: This is an informational message, and no action is required.

HALRT-01185: {0} automatically failed over to a spare disk. Status: {1} Manufacturer: {2} Model Number: {3} Size: {4} Serial Number: {5} Firmware: {6} Slot Number: {7} Cell Disk: {8} Grid Disk: {9} Flash Cache {10} Flash Log {11}.

Cause: The flash disk failed over to the spare disk.

Action: This is an informational message, and no action is required.

HALRT-01186: {0} was removed. Status: {1} Manufacturer: {2} Model Number: {3} Size: {4} Serial Number: {5} Firmware: {6} Slot Number: {7} Cell Disk: {8} Grid Disk: {9} Flash Cache {10} Flash Log {11}.

Level: Critical

Cause: A flash disk was removed.

Action: A flash disk was removed, or is no longer visible.

  • If the flash disk has been replaced, then this alert is informational only, and a flash disk replaced CLEAR alert will be sent. No action is needed.

  • If flash is being used as a cache, then the effect is that the flash cache size has reduced on the cell. Flash disk removal does not cause an outage, data loss, or Oracle ASM rebalance.

  • Each flash card contains four flash disks. If all four flash disks on a card send an alert, then the removal is likely for a card. To determine if the flash disks are on the same card, check for identical PCI slot numbers in the alert output.

HALRT-01187: {0} was replaced. Status: {1} Manufacturer: {2} Model Number: {3} Size: {4} Serial Number: {5} Firmware: {6} Slot Number: {7} Cell Disk: {8} Grid Disk: {9} Flash Cache {10} Flash Log {11}.

Level: Warning

Cause: The flash disk was replaced.

Action: This is an informational message, and no action is required.

HALRT--01188: {0} was replaced. Status: {1} Manufacturer: {2} Model Number: {3} Size: {4} Serial Number: {5} Firmware: {6} Slot Number: {7} Cell Disk: {8} Grid Disk: {9} Flash Cache {10} Flash Log {11}.Board Tracer Number : {12}.

Level: Warning

Cause: The flash disk was replaced.

Action: This is an informational message, and no action is required.

  • If the flash disk in this slot was previously used for flash cache, then the flash cache are automatically re-enabled.

  • If the flash disk in this slot was previously used for flash log, then the flash log are automatically re-enabled.

  • If the flash disk in this slot was previously used for grid disks, then the grid disks are automatically recreated and data will be automatically rebalanced by Oracle ASM.

HALRT--01189: Oracle Exadata Storage Server failed to auto-create cell disk and grid disks on the newly inserted physical disk. Physical Disk: {0} Status: {1} Manufacturer: {2} Model Number: {3} Size: {4} Serial Number: {5} Firmware: {6} Slot Number: {7} Board Tracer Number: {8}.

Level: Warning

Cause: The component was replaced.

Action: Oracle Exadata System Software continues to retry, and an alert is sent when the auto-create operation succeeds.

HALRT--01190: Previously missing {0} is found. Status: {1} Manufacturer: {2} Model Number: {3} Size: {4} Serial Number: {5} Firmware: {6} Slot Number: {7} Cell Disk: {8} Grid Disk: {9} Flash Cache {10} Flash Log {11} Board Tracer Number : {12}.

Level: Critical

Cause: The flash disk was located.

Action: This is an informational message, and no action is required.

  • If the flash disk in this slot was previously used for flash cache, then the flash cache are automatically re-enabled.

  • If the flash disk in this slot was previously used for flash log, then the flash log are automatically re-enabled.

  • If the flash disk in this slot was previously used for grid disks, then the grid disks are automatically recreated and data will be automatically rebalanced by Oracle ASM.

HALRT--01191: {0} status changed to normal. Status: {1} Manufacturer: {2} Model Number: {3} Size: {4} Serial Number: {5} Firmware: {6} Slot Number: {7} Cell Disk: {8} Grid Disk: {9} Flash Cache {10} Flash Log {11} Board Tracer Number : {12}.

Level: Warning

Cause: The flash disk status changed to normal.

Action: This is an informational message, and no action is required.

HALRT--01192: {0} was removed and inserted. Status: {1} Manufacturer: {2} Model Number: {3} Size: {4} Serial Number: {5} Firmware: {6} Slot Number: {7} Board Tracer Number : {9}.

Level: Informational

Cause: The physical disk was removed and inserted.

Action: This is an informational message, and no action is required. CELLSRV may have reported I/O errors when the disk was removed. If any grid disk on the physical disk went offline in Oracle ASM, then Oracle ASM automatically brings the disk online.

HALRT--01193: {0} failed. Status: {1} Manufacturer: {2} Model Number: {3} Size: {4} Serial Number: {5} Firmware: {6} Slot Number: {7} Cell Disk: {8} Grid Disk: {9} Board Tracer Number : {10}.

Level: Critical

Cause: A flash disk failed.

Action: The flash disk failed, and must be replaced. A white Locator LED has been lit to help locate the affected cell.

  • If the flash disk is used for flash cache, then flash cache is disabled on this disk, reducing the effective flash cache size.

  • If flash cache is in write back mode, then dirty data on this flash disk is automatically flushed to the corresponding grid disks.

  • If the flash disk is used for flash log, then flash log is disabled on this disk, reducing the effective flash log size.

  • If the flash disk is used for grid disks, then the data from the flash disk is automatically rebalanced by Oracle ASM to other flash disks.

HALRT--01194: {0} entered predictive failure status. Status: {1} Manufacturer: {2} Model Number: {3} Size: {4} Serial Number: {5} Firmware: {6} Slot Number: {7} Cell Disk: {8} Grid Disk: {9} Flash Cache {10} Flash Log {11} Board Tracer Number : {12}.

Level: Critical

Cause: The flash disk entered predictive failure status.

Action: The flash disk has entered predictive failure status. A white Locator LED has been lit to help locate the affected cell.

  • If the flash disk is used for flash cache, then flash cache is disabled on this disk, reducing the effective flash cache size.

  • If flash cache is in write back mode, then dirty data on this flash disk is automatically flushed to the corresponding grid disks.

  • If the flash disk is used for flash log, then flash log is disabled on this disk, reducing the effective flash log size.

  • If the flash disk is used for grid disks, then the data from the flash disk is automatically rebalanced by Oracle ASM to other flash disks.

Another alert will be sent when all data has been rebalanced and flushed from this flash disk. Wait until rebalance and flush have completed before replacing the flash disk.

HALRT--01195: {0} entered peer failure status. Status: {1} Manufacturer: {2} Model Number: {3} Size: {4} Serial Number: {5} Firmware: {6} Slot Number: {7} Cell Disk: {8} Grid Disk: {9} Flash Cache {10} Flash Log {11} Board Tracer Number : {12}.

Level: Critical

Cause: The flash disk entered peer failure status.

Action: The flash disk has entered predictive failure status. A white Locator LED has been lit to help locate the affected cell.

  • If the flash disk is used for flash cache, then flash cache is disabled on this disk, reducing the effective flash cache size.

  • If flash cache is in write back mode, then dirty data on this flash disk is automatically flushed to the corresponding grid disks.

  • If the flash disk is used for flash log, then flash log is disabled on this disk, reducing the effective flash log size.

  • If the flash disk is used for grid disks, then the data from the flash disk is automatically rebalanced by Oracle ASM to other flash disks.

Another alert will be sent when all data has been rebalanced and flushed from this flash disk. Wait until rebalance and flush have completed before replacing the flash disk.

HALRT--01196: {0} entered write-through caching mode. Status: {1} Manufacturer: {2} Model Number: {3} Size: {4} Serial Number: {5} Firmware: {6} Slot Number: {7} Cell Disk: {8} Grid Disk: {9} Flash Cache {10} Flash Log {11} Board Tracer Number : {12}.

Level: Critical

Cause: The flash disk entered write-through caching mode.

Action: The flash disk has entered predictive failure status. A white Locator LED has been lit to help locate the affected cell.

  • If the flash disk is used for flash cache, then flash cache is disabled on this disk, reducing the effective flash cache size.

  • If flash cache is in write back mode, then dirty data on this flash disk is automatically flushed to the corresponding grid disks.

  • If the flash disk is used for flash log, then flash log is disabled on this disk, reducing the effective flash log size.

  • If the flash disk is used for grid disks, then the data from the flash disk is automatically rebalanced by Oracle ASM to other flash disks.

Another alert will be sent when all data has been rebalanced and flushed from this flash disk. Wait until rebalance and flush have completed before replacing the flash disk.

HALRT--01197: {0} sstatus changed to offline. Status: {1} Manufacturer: {2} Model Number: {3} Size: {4} Serial Number: {5} Firmware: {6} Slot Number: {7} Cell Disk: {8} Grid Disk: {9} Flash Cache {10} Flash Log {11} Board Tracer Number : {12}.

Level: Critical

Cause: The component status changed to offline.

Action: This is an informational message, and no action is required.

HALRT--01198: {0} automatically failed over to a spare disk. Status: {1} Manufacturer: {2} Model Number: {3} Size: {4} Serial Number: {5} Firmware: {6} Slot Number: {7} Cell Disk: {8} Grid Disk: {9} Flash Cache {10} Flash Log {11} Board Tracer Number : {12}.

Level: Critical

Cause: The component failed over to a spare disk.

Action: This is an informational message, and no action is required.

HALRT--01199: {0} was permanently removed. Cell was downgraded successfully. Status: {1} Manufacturer: {2} Model Number: {3} Size: {4} Serial Number: {5} Firmware: {6} Slot Number: {7} Cell Disk: {8} Grid Disk: {9} Flash Cache {10} Flash Log {11} Board Tracer Number : {12}.

Level: Clear

Cause: A flash disk was removed from its slot by a user. Cell was downgraded successfully.

Action: This is an informational message, and no action is required.

D.7 Accelerator/Controller Alert Messages: HALRT-01209 to HALRT-01300

These alert messages are in the range HALRT-01209 through HALRT-01300.

HALRT-01209, Alarm has been enabled by user for Adapter {0}.

Cause: An alarm was enabled for the adapter.

Action: This is an informational alert and no user action is specified.

HALRT-01210, Background initialization rate changed to {0} for Adapter {1}.

Cause: The background initialization rate was changed for the adapter.

Action: This is an informational alert and no user action is specified.

HALRT-01211, Controller {0} cache discarded due to memory/battery problems.

Cause: The controller cache was discarded due to memory or battery problems.

Action: Losing the cache implies that any data on the disks is now stale. Drop force the data on disks attached to this controller from Oracle ASM and then add them back.

HALRT-01212, Unable to recover Cache Data due to configuration mismatch for Adapter {0}.

Cause: Cache data was recovered due to a configuration mismatch.

Action: Losing the cache implies that any data on the disks is now stale. Drop force the data on disks attached to this controller from Oracle ASM and then add them back.

HALRT-01213, Cache Data Recovered for Adapter {0}.

Cause: Cache data was recovered for the adapter.

Action: This is an informational alert and no user action is specified.

HALRT-01214, Controller cache discarded due to firmware version incompatibility for Adapter {0}

Cause: Controller cache was discarded because of incompatibility with the firmware version.

Action: Losing the cache implies that any data on the disks is now stale. Drop force the data on disks attached to this controller from Oracle ASM and then add them back.

HALRT-01215, Consistency Check rate changed to {0} for Adapter {1}.

Cause: The consistency check rate was changed for the adapter.

Action: This is an informational alert and no user action is specified.

HALRT-01216, Flash downloaded image corrupted for Adapter {0}.

Cause: The flash memory card image was corrupted.

Action: Reflash the disk controller firmware.

HALRT-01217, Flash erase error for Adapter {0}.

Cause: There was a flash erase error for the adapter.

Action: Reflash the disk controller firmware.

HALRT-01218, Flash timeout during erase for Adapter {0}.

Cause: The flash timed out during the erase procedure.

Action: Reflash the disk controller firmware.

HALRT-01219, Flash error for Adapter {0}.

Cause: There was a flash error for the adapter.

Action: Reflash the disk controller firmware.

HALRT-01220, Flashing image: {0} for Adapter {1}.

Cause: The controller flash was upgraded with a new image.

Action: This is an informational alert and no user action is specified.

HALRT-01221, Flash of new firmware image(s) complete for Adapter {0}.

Cause: The new firmware image was copied to flash.

Action: This is an informational alert and no user action is specified.

HALRT-01222, Flash programming error for Adapter {0}.

Cause: There was a flash programming error for the adapter.

Action: Reflash the disk controller firmware.

HALRT-01223, Flash timeout during programming for Adapter {0}.

Cause: The flash timed out while programming of the adapter.

Action: Reflash the disk controller firmware.

HALRT-01224, Fatal error received for Adapter {0}.

Cause: A fatal error occurred.

Action: The disk controller is seeing errors. Contact Oracle Support Services.

HALRT-01225, Rebuild rate changed to {0} for Adapter {1}.

Cause: The rebuild rate changed for the adapter.

Action: This is an informational alert and no user action is specified.

HALRT-01226, Alarm has been disabled by user for Adapter {0}.

Cause: The alarm for the adapter was disabled.

Action: This is an informational alert and no user action is specified.

HALRT-01227, Configuration cleared for Adapter {0}.

Cause: The configuration for the adapter was cleared.

Action: If this change is unintentional, contact Oracle Support Services.

HALRT-01228, Factory defaults restored for Adapter {0}.

Cause: The factory default settings were restored for the adapter.

Action: If this change is unintentional, contact Oracle Support Services.

HALRT-01229, HDD disk controller battery not Present for Adapter {0}.

Cause: The battery was not present for the adapter.

Action: If this change is unintentional, contact Oracle Support Services.

HALRT-01230, New HDD disk controller battery Detected for Adapter {0}.

Cause: A new battery was detected for the adapter.

Action: This is an informational alert and no user action is specified.

HALRT-01231, HDD disk controller battery has been replaced for Adapter {0}.

Cause: The battery was replaced for the adapter.

Action: This is an informational alert and no user action is specified.

HALRT-01232, HDD disk controller battery temperature is high for Adapter {0}.

Cause: The battery temperature was high for the adapter.

Action: Ensure operating temperature is within specified levels for the machine.

HALRT-01233, HDD disk controller battery voltage low for Adapter {0}.

Cause: The battery voltage was low for the adapter.

Action: If the battery is not fully charged, then charge it. Otherwise, the battery might be about to fail. Replace disk controller battery.

HALRT-01234, HDD disk controller battery temperature is normal for Adapter {0}.

Cause: The battery temperature was normal for the adapter.

Action: This is an informational alert and no user action is specified.

HALRT-01235, HDD disk controller battery needs replacement, SOH Bad for Adapter {0}.

Cause: The battery needed replacement.

Action: If the battery is not fully charged, then charge it. Otherwise, the battery might be about to fail. Replace disk controller battery.

HALRT-01236, HDD disk controller battery removed for Adapter {0}.

Cause: The battery was removed for the adapter.

Action: If this change is unintentional, contact Oracle Support Services.

HALRT-01237, Current capacity of the HDD disk controller battery is below threshold for Adapter {0}.

Cause: The battery capacity was below the threshold for the adapter.

Action: If the battery is not fully charged, then charge it. Otherwise, the battery might be about to fail. Replace disk controller battery.

HALRT-01238, Current capacity of the HDD disk controller battery is above threshold for Adapter {0}.

Cause: The battery capacity was above the threshold for the adapter.

Action: This is an informational alert and no user action is specified.

HALRT-01239, Bbu FRU changed for Adapter {0}.

Cause: The battery backup unit (BBU) field replacement unit (FRU) changed for the adapter.

Action: This is an informational alert and no user action is specified.

HALRT-01240, The disk controller battery is executing a learn cycle and may temporarily enter WriteThrough Caching mode as part of the learn cycle. Disk write throughput might be temporarily lower during this time. The flash drives are not affected. The battery learn cycle is a normal maintenance activity that occurs quarterly and runs for approximately 1 to 12 hours. Note that many learn cycles do not require entering WriteThrough caching mode. When the disk controller cache returns to the normal WriteBack caching mode, an additional informational alert will be sent. Battery Serial Number: {1} Battery Type: {2} Battery Tempearature: {3} Full Charge Capacity: {4} Relative Charge: {5} Ambient Temperaturer: {6}.

Cause: Disk controller battery started the learn cycle.

Action: This is an informational message, and no action is required. This is a normal maintenance activity that occurs quarterly and runs for approximately 1 to 12 hours. The disk controller cache might go into write through caching mode during the learn cycle. Disk write throughput might be temporarily lower during this time.

HALRT-01243, All disk drives have been placed in WriteThrough caching mode. The flash drives are not affected. The disk controller battery is executing an unscheduled learn cycle. Battery Serial Number: {1} Battery Type: {2} Battery Tempearature: {3} Full Charge Capacity: {4} Relative Charge: {5} Ambient Temperaturer: {6}.

Cause: An unscheduled learn cycle started.

Action: Determine the reason for the unscheduled learn cycle.

HALRT-01244, HDD disk controller SAS lanes have encountered errors.

Cause: A problem was encountered for the hard disk drive disk controller SAS lanes.

Action: The disk controller is seeing errors. Contact Oracle Support Services.

HALRT-01245, HDD disk controller SAS lanes are back to normal.

Cause: The hard disk drive disk controller SAS lanes were normal.

Action: This is an informational message.

D.8 Voltage Alert Messages: HALRT-01301 to HALRT-01400

These messages are in the range HALRT-01301 to HALRT-01400.

HALRT-01301, Under-Voltage Problem (lower critical - going low).

Cause: There was an under-voltage problem.

Action: This is an informational alert and no user action is specified.

HALRT-01302, Under-Voltage Problem Cleared.

Cause: The under-voltage problem was cleared.

Action: This is an informational alert and no user action is specified.

HALRT-01303, Generic Critical Voltage Problem.

Cause: There was a generic voltage problem.

Action: This is an informational alert and no user action is specified.

HALRT-01304, Generic Critical Voltage Problem Cleared.

Cause: The generic voltage problem was cleared.

Action: This is an informational alert and no user action is specified.

D.9 Physical Disk Alert Messages: HALRT-01401 to HALRT-01500

These messages are in the range HALRT-01401 to HALRT-01500

HALRT-01401, {0} was replaced. Status: {1} Manufacturer: {2} Model Number: {3} Size: {4} Serial Number: {5} Firmware: {6} Slot Number: {7} Cell Disk: {8} Grid Disk: {9}.
LevelClear

Cause: The component was replaced in the rack.

Action: The grid disks are automatically recreated, and the data is automatically rebalanced by Oracle ASM.

HALRT-01402, {0} was replaced. Status: {1} Manufacturer: {2} Model Number: {3} Size: {4} Serial Number: {5} Firmware: {6} Slot Number: {7} Cell Disk: {8} Grid Disk: {9} Flash Cache: {10} Flash Log: {11}.
LevelClear

Cause: The flash disk was replaced in the rack.

Action: This is an informational message, and no action is required.

  • If the flash disk in this slot was previously used for flash cache, then flash cache will be automatically re-enabled.

  • If the flash disk in this slot was previously used for flash log, then flash log will be automatically re-enabled.

  • If the flash disk in this slot was previously used for grid disks, then grid disks will be automatically recreated and data will be automatically rebalanced by Oracle ASM.

HALRT-01403, {0} was replaced. Status: {1} Manufacturer: {2} Model Number: {3} Size: {4} Serial Number: {5} Firmware: {6} Slot Number: {7} Cell Disk: {8} Grid Disk: {9}.
LevelClear

Cause: The component was replaced in the rack.

Action: This is an informational message, and no action is required.

HALRT-01404, {0} was replaced. Status: {1} Manufacturer: {2} Model Number: {3} Size: {4} Serial Number: {5} Firmware: {6} Slot Number: {7} Cell Disk: {8} Grid Disk: {9} Flash Cache: {10} Flash Log: {11}.
LevelClear

Cause: The component was replaced in the rack.

Action: This is an informational message, and no action is required.

HALRT-01405, Oracle Exadata Storage Server failed to auto-create cell disk and grid disks on the newly inserted physical disk. Physical Disk: {0} Status: {1} Manufacturer: {2} Model Number: {3} Size: {4} Serial Number: {5} Firmware: {6} Slot Number: {7}.
LevelClear

Cause: The component was replaced in the rack.

Action: Oracle Exadata System Software continues to try to create the cell disk and grid disks. An alert is sent when the auto-creation succeeds.

HALRT-01406, {0} was replaced. Status: {1} Manufacturer: {2} Model Number: {3} Size: {4} Serial Number: {5} Firmware: {6} Slot Number: {7} Cell Disk: {8} Grid Disk: {9} Flash Cache: {10} Flash Log: {11} Board Tracer Number: {12}.
LevelClear

Cause: The component was replaced in the rack.

Action: This is an informational message, and no action is required.

HALRT-01407, {0} was replaced. Status: {1} Manufacturer: {2} Model Number: {3} Size: {4} Serial Number: {5} Firmware: {6} Slot Number: {7} Cell Disk: {8} Grid Disk: {9} Flash Cache: {10} Flash Log: {11} Board Tracer Number: {12}.
LevelClear

Cause: The flash disk was replaced in the rack.

Action: This is an informational message, and no action is required.

  • If the flash disk in this slot was previously used for flash cache, then flash cache will be automatically re-enabled.

  • If the flash disk in this slot was previously used for flash log, then flash log will be automatically re-enabled.

  • If the flash disk in this slot was previously used for grid disks, then grid disks will be automatically recreated and data will be automatically rebalanced by Oracle ASM.

HALRT-01408, Oracle Exadata Storage Server failed to auto-create cell disk and grid disks on the newly inserted physical disk. Physical Disk: {0} Status: {1} Manufacturer: {2} Model Number: {3} Size: {4} Serial Number: {5} Firmware: {6} Slot Number: {7} Board Tracer Number: {8}.
LevelClear

Cause: The component was replaced in the rack.

Action: Oracle Exadata System Software continues to try to create the cell disk and grid disks. An alert is sent when the auto-creation succeeds.

HALRT-01409, {0} status changed to normal. Status: {1} Manufacturer: {2} Model Number: {3} Size: {4} Serial Number: {5} Firmware: {6} Slot Number: {7} Cell Disk: {8} Grid Disk: {9}.
LevelClear

Cause: The component status changed to normal.

Action: This is an informational message, and no action is required.

HALRT-01410, {0} status changed to normal. Status: {1} Manufacturer: {2} Model Number: {3} Size: {4} Serial Number: {5} Firmware: {6} Slot Number: {7} Cell Disk: {8} Grid Disk: {9} Flash Cache: {10} Flash Log: {11}.
LevelClear

Cause: The component status changed to normal.

Action: This is an informational message, and no action is required.

HALRT-01411, {0} status changed to normal. Status: {1} Manufacturer: {2} Model Number: {3} Size: {4} Serial Number: {5} Firmware: {6} Slot Number: {7} Cell Disk: {8} Grid Disk: {9} Flash Cache: {10} Flash Log: {11} Board Tracer Number: {12} .
LevelClear

Cause: The component status changed to normal..

Action: This is an informational message, and no action is required.

HALRT-01420, {0} entered poor performance status. The LUN {1} changed status to {2}. CellDisk changed status to {3}. Status : {4} Manufacturer : {5} Model Number {6} Size : {7} Serial Number : {8} Firmware : {9} Slot Number : {10} Cell Disk : {11} Grid Disk : {12} Flash Cache : {13} Flash Log: {14} Reason for poor performance : {15} Board Tracer Number : {16}
LevelCritical

Cause: The hard disk or flash disk status changed to poor performance

Action:The flash disk has entered poor performance status. A white cell locator LED has been lit to help locate the affected cell.

If the flash disk is used for flash cache, then flash cache will be disabled on this disk thus reducing the effective flash cache size. If flash cache is in write back mode, dirty data on this flash disk will be automatically flushed to the corresponding grid disks. If the flash disk is used for flash log, then flash log will be disabled on this disk thus reducing the effective flash log size. If the flash disk is used for grid disks, then the data from the flash disk will be automatically rebalanced by Oracle ASM to other flash disks. Another alert will be sent when all data has been rebalanced and flushed from this flash disk. Please wait until rebalance and flush have completed before replacing the flash disk.

HALRT-01421, {0} entered poor performance status. The LUN {1} changed status to {2}. CellDisk changed status to {3}. Status : {4} Manufacturer : {5} Model Number {6} Size : {7} Serial Number : {8} Firmware : {9} Slot Number : {10} Cell Disk : {11} Grid Disk : {12} Reason for poor performance : {13}
LevelCritical

Cause: The hard disk or flash disk status changed to poor performance

Action: The physical disk at slot {0} demonstrates poor performance, and should be replaced. The Oracle ASM disks associated with the grid disks on this physical disk are automatically dropped with FORCE option if possible. If drop FORCE cannot succeed due to offline partners, then the grid disks are automatically dropped normally, and an Oracle ASM rebalance will relocate the data from the poor performance disk to other disks.

If the drop did not complete before the physical disk dies, then refer to "Replacing a Hard Disk Due to Disk Failure" or the alert message pertaining to the disk failure.

To replace a disk due to disk problems, perform the following procedure:

  1. Wait until the Oracle ASM disks associated with the grid disks on the physical disk have been successfully dropped. To determine if the grid disks have been dropped, query the V$ASM_DISK_STAT view on the Oracle ASM instance.

  2. Replace the physical disk. The physical disk is hot-pluggable, and can be replaced when the power is on.

    The grid disks and cell disk that existed on the previous disk in the slot will be re-created on the new physical disk. If those grid disks were part of an Oracle ASM disk group, then they will be added back to the disk group and the data will be rebalanced based on disk group redundancy and the asm_power_limit parameter.

Oracle ASM rebalance occurs when dropping or adding a disk. To check the status of the rebalance, do the following:

  • The rebalance operation may have been successfully run. Check the Oracle ASM alert logs to confirm.

  • The rebalance operation may be currently running. Check the GV$ASM_OPERATION view to determine if the rebalance operation is still running.

  • The rebalance operation may have failed. Check the ERROR_CODE column in the V$ASM_OPERATION view to determine if the rebalance operation failed.

  • Rebalance operations from multiple disk groups can be done on different Oracle ASM instances in the same cluster. One Oracle ASM instance can run one rebalance operation at a time. If all Oracle ASM instances are busy, then rebalance operations will be queued.

D.10 Auto Service Request Alert Messages for Exadata Storage Servers: HALRT-02001 to HALRT-02100

These messages are Auto Service Request alerts in the range HALRT-02001 to HALRT-02100.

HALRT-02001

Cause: The system disk has failed.

Action: An alert has been submitted to Oracle Support Services.

HALRT-02002

Cause: The system disk had a predictive failure.

Action: An alert has been submitted to Oracle Support Services.

HALRT-02003

Cause: A data disk has failed.

Action: An alert has been submitted to Oracle Support Services.

HALRT-02004

Cause: A data disk had a predictive failure.

Action: An alert has been submitted to Oracle Support Services.

HALRT-02005

Cause: A flash disk has failed.

Action: An alert has been submitted to Oracle Support Services.

HALRT-02006

Cause: A flash disk had a predictive failure.

Action: An alert has been submitted to Oracle Support Services.

HALRT-02007

Cause: A hard disk in a database server has failed.

Action: An alert has been submitted to Oracle Support Services.

HALRT-02008

Cause: A hard disk in a database server had a predictive failure.

Action: An alert has been submitted to Oracle Support Services.

HALRT-02009

Cause: System hard disk had poor performance.

Action: An alert has been submitted to Oracle Support Services.

HALRT-02010

Cause: Data hard disk had poor performance.

Action: An alert has been submitted to Oracle Support Services.

HALRT-02011

Cause: Flash disk had poor performance.

Action: An alert has been submitted to Oracle Support Services.

HALRT-02012

Cause: The BBU failed.

Action: An alert has been submitted to Oracle Support Services.

HALRT-02013

Cause: The BBU degraded for unknown reasons.

Action: An alert has been submitted to Oracle Support Services.

HALRT-02014

Cause: Flash disk failed.

Action: An alert has been submitted to Oracle Support Services.

HALRT-02015

Cause: Flash disk had a predictive failure.

Action: An alert has been submitted to Oracle Support Services.

HALRT-02016

Cause: Flash disk had poor performance.

Action: An alert has been submitted to Oracle Support Services.

HALRT-02017

Cause: The USB is not present.

Action: An alert has been submitted to Oracle Support Services.

HALRT-02018

Cause: The USB failed.

Action: An alert has been submitted to Oracle Support Services.

HALRT-02019

Cause: The USB degraded for unknown reasons.

Action: An alert has been submitted to Oracle Support Services.

HALRT-02020

Cause: Flash disk failed.

Action: An alert has been submitted to Oracle Support Services.

HALRT-02021

Cause: Flash disk had a predictive failure.

Action: An alert has been submitted to Oracle Support Services.

HALRT-02022

Cause: Flash disk had poor performance.

Action: An alert has been submitted to Oracle Support Services.

HALRT-02023

Cause: The Cache Vault failed.

Action: An alert has been submitted to Oracle Support Services.

HALRT-02024

Cause: The Cache Vault degraded for unknown reasons.

Action: An alert has been submitted to Oracle Support Services.

HALRT-02025

Cause: The hard disk controller flash memory failed.

Action: An alert has been submitted to Oracle Support Services.

HALRT-02026

Cause: Flash disk failed.

Action: An alert has been submitted to Oracle Support Services.

HALRT-02027

Cause: Flash disk had a predictive failure.

Action: An alert has been submitted to Oracle Support Services.

HALRT-02028

Cause: Flash disk had poor performance.

Action: An alert has been submitted to Oracle Support Services.

HALRT-02029

Cause: The M.2 disk failed.

Action: An alert has been submitted to Oracle Support Services.

D.11 HDD Controller Battery Alert Messages: HALRT-02101 to HALRT-02200

These messages are HDD controller battery messages in the range of HALRT-02101 to HALRT-02200.

HALRT-02101, The HDD disk controller battery was dropped for replacement. All disk drives have been placed in WriteThrough caching mode. Disk write performance may be reduced. The flash drives are not affected Battery Serial Number : {0} Battery Type: {1} Battery Temperature: {2} Full Charge Capacity : {3} Relative Charge: {4} Ambient Temperature: {5}.

Level: Warning

Cause: The HDD disk controller was dropped prior to replacement.

Action: Replace the HDD disk controller battery or re-enable the HDD disk controller battery using the ALTER CELL BBU REENABLE command if the HDD disk controller battery was dropped in error.

HALRT-02102, HDD disk controller battery is {0}. All disk drives have been placed in WriteThrough caching mode. Disk write performance may be reduced. The flash drives are not affected. Battery Serial Number : {1} Battery Type: {2} Battery Temperature: {3} Full Charge Capacity : {4} Relative Charge: {5} Ambient Temperature: {6}.

Level: Critical

Cause: The HDD disk controller battery failed.

Action: Replace the HDD disk controller battery.

HALRT-02103, All disk drives have been temporarily placed in WriteThrough caching mode because HDD disk controller battery is performing a learn cycle. Disk write performance may be somewhat reduced. The flash drives are not affected. Battery Serial Number : {1} Battery Type: {2} Battery Temperature: {3} Full Charge Capacity : {4} Relative Charge: {5} Ambient Temperature: {6}.

Level: Informational

Cause: The HDD disk controller battery was performing a learn cycle.

Action: This is an informational alert. Disk drives will be in writeback mode when the HDD disk controller battery completes the learn cycle.

HALRT-02104, All disk drives have been temporarily placed in WriteThrough caching mode because HDD disk controller battery is charging. Disk write performance may be somewhat reduced. The flash drives are not affected. Battery Serial Number : {1} Battery Type: {2} Battery Temperature: {3} Full Charge Capacity : {4} Relative Charge: {5} Ambient Temperature: {6}.

Level: Informational

Cause: The HDD disk controller battery was charging.

Action: This is an informational alert. Disk drives will be in writeback mode when the HDD disk controller battery completes the charging.

HALRT-02105, The HDD disk controller battery was removed. All disk drives have been placed in WriteThrough caching mode. Disk write performance may be reduced. The flash drives are not affected.

Level: Informational

Cause: The HDD disk controller battery was removed.

Action: The HDD disk controller battery needs replacement.

HALRT-02106,The HDD disk controller battery capacity was under threshold value of {0} mAh. All disk drives have been placed in WriteThrough caching mode. Disk write performance may be reduced. The flash drives are not affected. Battery Serial Number : {1} Battery Type: {2} Battery Temperature: {3} Full Charge Capacity : {4} Relative Charge: {5} Ambient Temperature: {6}.

Level: Critical

Cause: The HDD disk controller battery capacity went too low.

Action: Replace the HDD disk controller battery or schedule a learn cycle.

HALRT-02107, The HDD disk controller battery temperature exceeded the threshold value of {6} Celsius. All disk drives have been placed in WriteThrough caching mode. Disk write performance may be reduced. The flash drives are not affected. Battery Serial Number : {1} Battery Type: {2} Battery Temperature: {3} Full Charge Capacity : {4} Relative Charge: {5} Ambient Temperature: {6}.

Level: Critical

Cause: The HDD disk controller battery temperature was too high.

Action: The HDD disk controller battery was overheated. Check if the ambient temperature is below {0} Celsius and if the fans are working.

HALRT-02108, All disk drives have been temporarily placed in WriteThrough caching mode because HDD disk controller battery was replaced. Disk write performance may be somewhat reduced. The flash drives are not affected. Battery Serial Number : {1} Battery Type: {2} Battery Temperature: {3} Full Charge Capacity : {4} Relative Charge: {5} Ambient Temperature: {6}.

Level: Informational

Cause: The HDD disk controller battery was replaced.

Action: This is an informational alert. Disk drives will be in writeback mode until the HDD disk controller battery completes charging.

HALRT-02109, All disk drives have been placed in WriteThrough caching mode. Disk write performance may be reduced. The flash drives are not affected. Battery Serial Number : {1} Battery Type: {2} Battery Temperature: {3} Full Charge Capacity : {4} Relative Charge: {5} Ambient Temperature: {6}.

Level: Critical

Cause: The HDD disk controller battery entered degraded or unknown status.

Action: Replace the HDD disk controller battery or schedule a learn cycle.

HALRT-02110, The HDD disk controller battery was removed before running the ALTER CELL BBU DROP FOR REPLACEMENT command. Battery Serial Number : {0} Battery Type: {1} Battery Temperature: {2} Full Charge Capacity : {3} Relative Charge: {4} Ambient Temperature: {5}.

Level: Critical

Cause: The HDD disk controller battery was removed, but the ALTER CELL BBU DROP FOR REPLACEMENT command was not run prior to removal of the battery.

Action: Replace the HDD disk controller battery.

HALRT-02111, The HDD disk controller battery was replaced. All disk drives are in WriteBack caching mode. Battery Serial Number : {0} Battery Type: {1} Battery Temperature: {2} Full Charge Capacity : {3} Relative Charge: {4} Ambient Temperature: {5}.

Level: Clear

Cause: The HDD disk controller battery was replaced.

Action: This is an informational alert and no user action is specified.

HALRT-02112, All disk drives are in WriteBack caching mode. Battery Serial Number : {0} Battery Type: {1} Battery Temperature: {2} Full Charge Capacity : {3} Relative Charge: {4} Ambient Temperature: {5}.

Level: Clear

Cause: The HDD disk controller battery returned to normal.

Action: This is an informational alert and no user action is specified.

HALRT-02113, All disk drives have been placed in WriteThrough caching mode. The controller has preserved cache for a disk drive for more than five minutes. The flash drives are not affected. Battery Serial Number : {0} Battery Type: {1} Battery Temperature: {2} Full Charge Capacity : {3} Relative Charge: {4} Ambient Temperature: {5}.

Level: Critical

Cause: All disk drives were placed in writethrough caching mode because of preserved cache.

Action: Contact Oracle Support Services.

HALRT-02114, The HDD disk controller battery is performing an unscheduled learn cycle. All disk drives have been placed in WriteThrough caching mode. The flash drives are not affected. Battery Serial Number : {0} Battery Type: {1} Battery Temperature: {2} Full Charge Capacity : {3} Relative Charge: {4} Ambient Temperature: {5}.

Level: Informational

Cause: The HDD disk controller battery performed an unscheduled learn cycle.

Action: Determine the cause of the unscheduled learn cycle.

HALRT-02115, Disk drive {0} is in WriteThrough caching mode. Write performance on this drive will be affected.

Level: Critical

Cause: Disk drive {0} entered writethrough caching mode.

Action: The HDD disk controller battery is good, but disk drive {0} is in writethrough caching mode. Contact Oracle Support Services.

HALRT-02116, Disk drive {0} is back in WriteBack caching mode.

Level: Clear

Cause: Disk drive {0} returned to writeback caching mode.

Action: This is an informational alert.

HALRT-02117, The HDD disk controller battery is performing a learn cycle. Battery Serial Number: {0} Battery Type: {1} Battery Temperature: {2} Full Charge Capacity: {3} Relative Charge: {4} Ambient Temperature: {5}.

Level: Informational

Cause: The hard disk controller battery entered a learn cycle.

Action: This is an informational alert, and no user action is needed.

All disk drives may temporarily enter writethrough caching mode as part of the learn cycle. Disk write throughput may be lower during this time. The flash drives are not affected.

The battery learn cycle is a normal maintenance activity that occurs quarterly, and runs for approximately 1 to 12 hours. Many learn cycles do not require entering writethrough caching mode. When the disk controller cache returns to writeback caching mode, an informational alert will be sent.

HALRT-02118, The HDD disk controller battery was replaced. All disk drives are in WriteBack caching mode. Battery Serial Number: {0} Battery Type: {1} Battery Temperature: {2} Full Charge Capacity: {3} Relative Charge: {4} Ambient Temperature: {5}.

Level: Informational

Cause: The hard disk controller battery was replaced.

Action: This is an informational alert, and no user action is needed.

HALRT-02119, The HDD disk controller battery was replaced. Battery Serial Number: {0} Battery Type: {1} Battery Temperature: {2} Full Charge Capacity: {3} Relative Charge: {4} Ambient Temperature: {5}.

Level: Informational

Cause: The hard disk controller battery was replaced.

Action: This is an informational alert, and no user action is needed.

HALRT-02120, The HDD disk controller battery was inserted back. Battery Serial Number: {0} Battery Type: {1} Battery Temperature: {2} Full Charge Capacity: {3} Relative Charge: {4} Ambient Temperature: {5}.

Level: Informational

Cause: The HDD disk controller was inserted.

Action: This is an informational alert, and no user action is needed.

HALRT-02121, HDD disk controller battery inserted back.

Level: Informational

Cause: The HDD disk controller was inserted.

Action: This is an informational alert, and no user action is needed.

HALRT-02121, The HDD disk controller battery was replaced. All disk drives are in WriteBack caching mode.

Level: Informational

Cause: The HDD disk controller was replaced.

Action: This is an informational alert, and no user action is needed.

HALRT-02122, All disk drives are in WriteBack caching mode. Battery Serial Number: {0} Battery Type: {1} Battery Temperature: {2} Full Charge Capacity {3} Relative Charge {4} Ambient Temperature: {5}

Level: Informational

Cause: The HDD disk controller battery is back to normal.

Action: This is an informational alert, and no user action is needed.

HALRT-02151, The HDD disk controller battery was dropped for replacement. All disk drives have been placed in WriteThrough caching mode. Disk write performance may be reduced. The flash drives are not affected. Battery Serial Number: {0} Battery Type: {1} Battery Temperature: {2} Pack Energy: {3} Ambient Temperature: {4}.

Level: Warning

Cause: The HDD disk controller was dropped for replacement.

Action: Replace the HDD disk controller battery, or reenable the HDD disk controller battery using the ALTER CELL BBU REENABLE command if the HDD disk controller battery was dropped in error.

HALRT-02152, The HDD disk controller battery has failed. All disk drives have been placed in WriteThrough caching mode. Disk write performance may be reduced. The flash drives are not affected. Battery Serial Number: {0} Battery Type: {1} Battery Temperature: {2} Pack Energy: {3} Ambient Temperature: {4}.

Level: Critical

Cause: The HDD disk controller battery failed.

Action: Replace the HDD disk controller battery.

HALRT-02153, All disk drives have been temporarily placed in WriteThrough caching mode because the HDD disk controller battery is performing a learn cycle. Disk write performance may be reduced. The flash drives are not affected. Battery Serial Number: {0} Battery Type: {1} Battery Temperature: {2} Pack Energy: {3} Ambient Temperature: {4}.

Level: Informational

Cause: The HDD disk controller battery was performing a learn cycle.

Action: No action is required. Disk drives are in writeback mode when the HDD disk controller battery completes the learn cycle.

HALRT-02154, All disk drives have been temporarily placed in WriteThrough caching mode because the HDD disk controller battery is charging. Disk write performance may be reduced. The flash drives are not affected. Battery Serial Number: {0} Battery Type: {1} Battery Temperature: {2} Pack Energy: {3} Ambient Temperature: {4}.

Level: Informational

Cause: The HDD disk controller battery entered charging mode.

Action: No action is required. Disk drives are in writeback mode until the HDD disk controller battery completes charging.

HALRT-02155, The HDD disk controller battery was removed. All disk drives have been placed in WriteThrough caching mode. Disk write performance may be reduced. The flash drives are not affected. Battery Serial Number: {0} Battery Type: {1} Battery Temperature: {2} Pack Energy: {3} Ambient Temperature: {4}.

Level: Informational

Cause: The HDD disk controller battery was removed.

Action: Replace the HDD disk controller battery.

HALRT-02156, The HDD disk controller battery has current capacity under threshold value of {0} Joule. All disk drives have been placed in WriteThrough caching mode. Disk write performance may be reduced. The flash drives are not affected. Battery Serial Number: {1} Battery Type: {2} Battery Temperature: {3} Pack Energy: {4} Ambient Temperature: {5}.

Level: Critical

Cause: The HDD disk controller battery charge was below the threshold value.

Action: Replace the HDD disk controller battery or schedule a learn cycle.

HALRT-02157, The HDD disk controller battery temperature exceeded the threshold value of {0} Celsius. All disk drives have been placed in WriteThrough caching mode. Disk write performance may be reduced. The flash drives are not affected. Battery Serial Number: {1} Battery Type: {2} Battery Temperature: {3} Pack Energy: {4} Ambient Temperature: {5}.

Level: Critical

Cause: The HDD disk controller battery temperature was above the threshold value.

Action: The HDD Disk controller battery has overheated. Ensure the ambient temperature is below {0} Celsius, and that the fans are working.

HALRT-02158, All disk drives were temporarily placed in WriteThrough caching mode because the HDD disk controller battery was replaced. Disk write performance may be reduced. The flash drives are not affected. Battery Serial Number: {1} Battery Type: {2} Battery Temperature: {3} Pack Energy: {4} Ambient Temperature: {5}.

Level: Informational

Cause: The HDD disk controller was replaced.

Action: No action is required. Disk drives are in writeback mode until the HDD disk controller battery completes charging.

HALRT-02159, All disk drives have been placed in WriteThrough caching mode. Disk write performance may be reduced. The flash drives are not affected. Battery Serial Number: {1} Battery Type: {2} Battery Temperature: {3} Pack Energy: {4} Ambient Temperature: {5}.

Level: Critical

Cause: All disk drives were placed in writethrough caching mode.

Action: Replace the HDD disk controller battery, or schedule a learn cycle.

HALRT-02161, The HDD disk controller battery was replaced. All disk drives are in WriteBack caching mode. Battery Serial Number: {1} Battery Type: {2} Battery Temperature: {3} Pack Energy: {4} Ambient Temperature: {5}.

Level: Informational

Cause: The HDD disk controller battery was replaced.

Action: This is an informational alert, and no user action is needed.

HALRT-02162, All disk drives are in WriteBack caching mode. Battery Serial Number: {1} Battery Type: {2} Battery Temperature: {3} Pack Energy: {4} Ambient Temperature: {5}.

Level: Informational

Cause: All disk drives were in writeback caching mode.

Action: This is an informational alert, and no user action is needed.

HALRT-02163, All disk drives have been placed in WriteThrough caching mode. The controller has preserved cache for a disk drive for more than five minutes. The flash drives are not affected. Battery Serial Number: {1} Battery Type: {2} Battery Temperature: {3} Pack Energy: {4} Ambient Temperature: {5}.

Level: Critical

Cause: All disk drives were placed in writethrough caching mode.

Action: Contact Oracle Support Services.

HALRT-02164, The HDD disk controller battery is performing unscheduled learn cycle. All disk drives have been placed in WriteThrough caching mode. The flash drives are not affected. Battery Serial Number: {1} Battery Type: {2} Battery Temperature: {3} Pack Energy: {4} Ambient Temperature: {5}.

Level: Informational

Cause: The HDD disk controller battery started an unscheduled learn cycle.

Action: Determine how the unscheduled learn cycle was started.

HALRT-02165, Disk drive {0} is in WriteThrough caching mode. Write performance on this drive will be affected. Battery Serial Number: {1} Battery Type: {2} Battery Temperature: {3} Pack Energy: {4} Ambient Temperature: {5}.

Level: Critical

Cause: The disk drive was in writethrough caching mode.

Action: Contact Oracle Support Services. The HDD disk controller battery is good, but disk drive {0} is in writethrough caching mode.

HALRT-02166, Disk drive {0} returned to WriteBack caching mode.

Level: Clear

Cause: The disk drive returned to writeback caching mode.

Action: This is an informational alert, and no user action is needed.

HALRT-02167, The HDD disk controller battery is performing a learn cycle. Battery Serial Number: {1} Battery Type: {2} Battery Temperature: {3} Pack Energy: {4} Ambient Temperature: {5}.

Level: Informational

Cause: The HDD disk controller started a learn cycle.

Action: The battery learn cycle is a normal maintenance activity that occurs quarterly, and runs for approximately 1 to 12 hours. Many learn cycles do not require entering writethrough caching mode. When the disk controller cache returns to the normal writeback caching mode, an informational alert is sent.

HALRT-02168, The HDD disk controller battery was replaced. All disk drives are in WriteBack caching mode. Battery Serial Number: {1} Battery Type: {2} Battery Temperature: {3} Pack Energy: {4} Ambient Temperature: {5}.

Level: Informational

Cause: The HDD disk controller battery was replaced.

Action: This is an informational alert, and no user action is needed.

HALRT-02169, The HDD disk controller battery was replaced. Battery Serial Number: {1} Battery Type: {2} Battery Temperature: {3} Pack Energy: {4} Ambient Temperature: {5}.

Level: Informational

Cause: The HDD disk controller battery was replaced.

Action: This is an informational alert, and no user action is needed.

HALRT-02170, The HDD disk controller battery was inserted back. Battery Serial Number: {1} Battery Type: {2} Battery Temperature: {3} Pack Energy: {4} Ambient Temperature: {5}.

Level: Informational

Cause: The HDD disk controller battery was inserted.

Action: This is an informational alert, and no user action is needed.

HALRT-02171, The HDD disk controller battery was replaced. All disk drives are in WriteBack caching mode. Battery Serial Number: {1} Battery Type: {2} Battery Temperature: {3} Pack Energy: {6} Ambient Temperature: {5}

Level: Informational

Cause: The HDD disk controller battery was replaced.

Action: This is an informational alert, and no user action is needed.

HALRT-02172, All disk drives are in WriteBack caching mode. Battery Serial Number: {1} Battery Type: {2} Battery Temperature: {3} Pack Energy: {6} Ambient Temperature: {5}.

Level: Informational

Cause: The HDD disk controller battery is back to normal.

Action: This is an informational alert, and no user action is needed.

HALRT-02190, The hard disk controller's flash memory failed so all disk drives will be placed in WriteThrough caching mode.

Level: Critical

Cause: The hard disk controller's flash memory failed.

Action: Replace the disk controller.

Detailed information on this problem can be found in My Oracle Support Doc ID 2285515.1

HALRT-02191, The hard disk controller was replaced.

Level: Informational

Cause: The hard disk controller was replaced.

Action: This is an informational alert, and no user action is needed.

D.12 USB and Hardware Configuration Alert Messages: HALRT-02401 to HALRT-02550

These alert messages are in the range HALRT-02401 through HALRT-02550.

HALRT-02401, Internal USB status is degraded. Contact Oracle Support.

Level: Critical

Cause: The USB was degraded.

Action: Contact Oracle Support Services.

HALRT-02402, Internal USB status is not present.

Level: Critical

Cause: The USB was not located.

Action: Contact Oracle Support Services.

HALRT-02403, Internal USB status is failed.

Level: Critical

Cause: The USB failed.

Action: Contact Oracle Support Services.

HALRT-02404, Internal USB status is back to normal.

Level: Informational

Cause: The USB was fixed.

Action: This is an informational message.

HALRT-02501, Check for configuration of {0} is successful.

Level: Informational

Cause: The hardware configuration changed.

Action: This is an informational message.

HALRT-02502, {0} check has detected the following issue(s): Attribute Name: {1}, Required: {2}, Found: {3}

Level: Critical

Cause: CELLCLI or DBMCLI detected a hardware configuration mismatch for a storage server or database server.

Action: Correct the configuration problems. Then run the command: ALTER {CELL | DBSERVER} VALIDATE CONFIGURATION

Verify that the new configuration is correct.

D.13 Generic Actions for Alert Messages: HALRT-10001 to HALRT-10500

These messages are user actions for alert messages. The actions are in the range HALRT-10001 through HALRT-10500.

HALRT-10001

Cause: There was a nonerror change for a hardware status, such as a return to normal status.

Action: This is an informational alert and no user action is specified.

HALRT-10003

Cause: An unscheduled learn cycle was started.

Action: Examine how the unscheduled learn cycle was started.

HALRT-10004

Cause: Temperature was not in the acceptable range.

Action: Shut down the system. Determine cause of the thermal failure. If necessary, move data out of this cell.

HALRT-10005

Cause: There was a problem with the fan.

Action: Shut down the system. Determine the cause of the fan failure. Replace the fan. If necessary, move data out of this cell.

HALRT-10007

Cause: There was a problem with the power supply.

Action: Examine the power supply. Replace the power supply if necessary.

HALRT-10015

Cause: Temperature was not in the acceptable range.

Action: Examine the thermal degradation. Shut down the system and move data out of this cell.

HALRT-10025

Cause: A CPU error was detected.

Action: Shut down system. Examine CPU error.

HALRT-10029, A generic sensor has detected an error.

Cause: There was a sensor change or error.

Action: Examine the sensor state change or error. If it is unexpected and has not been cleared yet, contact Oracle Support Services.

HALRT-10030

Cause: There was an alert.

Action: Refer to the additional information in the alert message.

HALRT-10031

Cause: The FRU was removed.

Action: If the FRU is not intentionally removed, contact Oracle Support Services.

HALRT-10032

Cause: There was an error.

Action: Capture any error message on the console. Restart or power cycle the system and try to bring it back to operation. Contact Oracle Support Services with the error messages.

HALRT-10033

Cause: The cache was lost.

Action: Losing the cache implies that any data on the disks is now stale. Drop force the data on disks attached to this controller from Oracle ASM and then add them back.

HALRT-10034

Cause: The disk controller firmware needed a refresh.

Action: Reflash the disk controller firmware.

HALRT-10035

Cause: The disk controller noticed errors.

Action: The disk controller is seeing errors. Contact Oracle Support Services.

HALRT-10036

Cause: There was a change to the system.

Action: If this change is unintentional, contact Oracle Support Services.

HALRT-10037

Cause: The operating temperature was not within the specified range for the machine.

Action: Ensure operating temperature is within specified levels for the machine.

HALRT-10038

Cause: The battery was not fully charged.

Action: If the battery is not fully charged, then charge it. Otherwise, the battery might be about to fail. Replace disk controller battery.

HALRT-10039

Cause: The LUN on the virtual drive has failed.

Action: The LUN on this virtual drive has failed. Drop the LUN and re-create it.

HALRT-10040

Cause: The physical disk was removed.

Action: If the physical drive was removed unintentionally, replace it back immediately.

HALRT-10041

Cause: The disk was not supported or certified for the system.

Action: Replace this disk with a supported and certified disk.

HALRT-10045

Cause: The flash write performance was degraded.

Action: The flash disk, flash PCI card or ESM should be replaced. If all disks on the PCI card show degraded performance, then the card should be replaced. Check the ESM LED on the PCI card. It is visible from the back of the cell chassis. If this LED is amber, then the card should be replaced.

Note:

This message may include text from message HALRT_10046 if there are grid disks, or from message HALRT_10047 if there are no grid disks but the cell disk is used for flash cache.

HALRT-10046

Cause: There was an error with the disk.

Action: If the disks being replaced have persistent data, then rebalance data out of these disks, and replace the flash disk. If there was persistent data on the flash disks, then rebalance data back into the disks.

HALRT-10047

Cause: There was an error with the flash disk.

Action: The Flash Cache portion provided by the flash disk will be automatically disabled.

HALRT-10054

Cause: The physical disk demonstrated extremely poor performance.

Action: The physical disk should be replaced at the earliest opportunity.

HALRT-10056

Cause: Auto Service Request was notified with a unique identifier.

Action: This is an informational alert, and no user action is needed.

HALRT-10057

Cause: Detailed information on this problem can be found at My Oracle Support.

Action: Refer to the My Oracle Support note listed in the alert.

HALRT-10066

Cause: The system hard disk demonstrated extremely poor performance.

Action: Replace the system hard disk as soon as possible.

HALRT-10067

Cause: The data hard disk demonstrated extremely poor performance.

Action: Replace the data hard disk as soon as possible.

HALRT-10068

Cause: The flash disk demonstrated extremely poor performance.

Action: Replace the flash disk as soon as possible.

HALRT-10073

Cause: The device monitoring utilities had unexpected output.

Action: A resolved alert will be sent when the problem is resolved. If the problem persists, then contact Oracle Support Services.

HALRT-10074

Cause: A flash disk was removed or was no longer visible to Oracle Exadata Storage Server Software.

Action: If the flash disk has just been replaced, then this alert is informational only. If the flash disk is being used as a cache, then the flash cache size has been reduced on this cell. Flash disk removal will not cause an outage, data loss, or Oracle ASM rebalance.

HALRT-10075

Cause: The temperature for Oracle Exadata Database Machine is outside the operating range.

Action: Oracle Exadata Database Machine has an operating range of 5 to 32 degrees Celsius (41 to 89.6 degrees Fahrenheit). Adjust the data center conditions so Oracle Exadata Database Machine is operating in its specified range.

HALRT-10076

Cause: The Oracle ASM disks associated with the grid disks on the physical disk were successfully dropped, and a blue OK to Remove LED was lit on the disk to indicate it is safe to remove the disk.

Action: Replace the disk drive at the earliest opportunity.

HALRT-10078

Cause: CELLSRV reported I/O errors when the physical disk was removed.

Action: No user action is needed. If a grid disk on this physical disk went offline in Oracle ASM as a result, then Oracle ASM will automatically bring the disk online.

HALRT-10079

Cause: The single system disk in the Exadata Storage Server did not have valid partitions.

Action: Contact Oracle Support Services.

HALRT-10080

Cause: A disk was inserted in the wrong slot.

Action: Insert the disk into the correct slot.

HALRT-10081

Cause: The hard disk demonstrated temporary poor performance. The disk has been confined and is in an offline state.

Action: If the hard disk was used for grid disks, then the Oracle ASM disks associated with the grid disks on this hard disk are offlined. Confinement tests run on this disk, and either move the disk permanently to poor performance or return the disk back to normal state.

HALRT-10082

Cause: The flash disk demonstrated temporary poor performance. The disk has been confined and is in an offline state.

Action: One of the following actions is performed:

  • If the flash disk was used for writethrough flash cache, then flash cache on this disk will be disabled causing a reduction in the effective flash cache size.

  • If the flash disk was used for writeback flash cache, then flash cache on this disk will be disabled, and read I/O to dirty data in the flash cache will go to the mirror disks on different cells. Write I/Os will go directly to the grid disks on this cell.

  • If the flash disk was used for flash log, then flash log is disabled on this disk causing a reduction of the effective flash log size.

  • If the flash disk was used for grid disks, then the Oracle ASM disks associated with the grid disks on this flash disk are offlined.

Confinement tests run on this disk, and either move the disk permanently to poor performance or return the disk back to normal state.

HALRT-10086

Cause: The flash disk has entered peer failure status. A white cell locator LED has been lit to help locate the affected cell.

Action: Another alert will be sent when all data has been rebalanced and flushed from the flash disk. Wait until the rebalance and flush operations are completed before replacing the flash disk indicated by the white LED.

HALRT-10087

Cause: The data on this disk has been successfully rebalanced and flushed.

Action: Replace the drive.

D.14 Generic Actions for Alert Messages: HALRT-10503 to HALRT-11000

These messages are user actions for alert messages. The actions are in the range HALRT-10503 through HALRT-11000.

HALRT-10503

Cause: The HDD disk controller had a problem.

Action: HDD disk controller battery needs replacement. Contact Oracle Support Services.

HALRT-10504

Cause: The battery was in write through caching mode.

Action: HDD disk controller battery is good, but logical drive is in write through caching mode. Contact Oracle Support Services

HALRT-10505

Cause: Disk controller battery completed the learn cycle.

Action: Disk controller battery is back to a good state, but disk drive is in writethrough caching mode. Contact Oracle Support Services.

HALRT-10506

Cause: Disk drive entered writeback caching mode.

Action: Disk drive is in writeback caching mode. No action is needed.

HALRT-10507

Cause: All logical drives were in write through caching mode.

Action: Disk controller battery is good, but all logical drives are in write through caching mode. Contact Oracle Support Services.

HALRT-10510

Cause: The contents of the disk controller cache have been lost.

Action: The contents of the disk controller cache have been lost, potentially leading to some loss of recent write operations. Access to the grid disks on this cell has been disabled. Oracle Exadata System Software disk auto management has been disabled for the cell to avoid potential conflicts with user-initiated disk offline or drop force during the recovery period. Auto management on the cells which do not have this problem is not affected. Contact Oracle Support Services.

HALRT-10511

Cause: New battery was being charged.

Action: The new battery is being automatically charged. When the battery completes charging the disk drives will be in writeback caching mode. This is an informational message, and no action is required.

HALRT-10512

Cause: Disk controller battery overheated.

Action: Disk controller battery is over-heated. Check if the ambient temperature is below 32 degrees Celsius and if the fans are working.

HALRT-10513

Cause: Disk controller battery was not functioning.

Action: Disk controller battery needs replacement.

D.15 Generic Actions for Alert Messages: HALRT-11001 to HALRT-11100

These messages are user actions for alert messages. The actions are in the range HALRT-11001 through HALRT-11100.

HALRT-11001

Cause: There was a problem with the InfiniBand configuration.

Action: Use ibstatus to check the InfiniBand configuration, and verify that both ports show state ACTIVE and the expected Gb per second. The alert is cleared when the port status is ACTIVE. One potential common cause for the InfiniBand link negotiating to a lower link rate is that the InfiniBand cable connectors on the HCA or the switch are loose. Ensuring the InfiniBand connector fits tightly in the HCA, and the switch usually solves this problem.

A port may show status DOWN after a switch reboot. The port is automatically made ACTIVE after a few minutes.

HALRT-11002

Cause: There was a problem with the InfiniBand port.

Action: Use the CellCLI command LIST IBPORT DETAIL to check the port. Verify both ports show zero error counts for rcvErrs and symbolErrs. A non-zero error count can be caused by a bad cable or a cable that is not properly seated. It can also be caused by a bad port on the HCA or switch. Manually disabling and enabling InfiniBand ports or resetting InfiniBand switches can also lead to these errors. Correct the problem, and then reset the InfiniBand error counts using the CellCLI command ALTER IBPORT...RESET. Error counts should be reset on both the HCA port and the peer switch port.

HALRT-11003

Cause: There was a problem with the InfiniBand port.

Action: Use the CellCLI command LIST IBPORT DETAIL to check the port. Verify that both ports show the expected Gb per second. A common cause for the InfiniBand link negotiating to a lower link rate is that the InfiniBand cable connectors on the HCA or the switch are loose. Ensuring the InfiniBand connector fits tightly in the HCA and in the switch usually solves this problem.

D.16 MS on Database Server Alert Messages: HALRT-20000 to HALRT-21000

These messages are user actions for alert messages. The alerts are in the range HALRT-20000 to HALRT-21000.

HALRT-20000: {0} was removed. Status: {1}, Manufacturer: {2}, Model Number: {3}, Size: {4}, Serial Number: {5}, Firmware: {6}, Slot Number: {7}

Cause: A hard disk or flash disk of size {4} in slot {7} was removed.

Action: Informational message. No action required.

HALRT-20001: {0} was replaced. Status: {1}, Manufacturer: {2}, Model Number: {3}, Size: {4}, Serial Number: {5}, Firmware: {6}, Slot Number: {7}

Cause: A hard disk or flash disk of size {4} in slot {7} was replaced.

Action: Informational message. No action required.

HALRT-20002: Previously missing {0} is found. Status: {1}, Manufacturer: {2}, Model Number: {3}, Size: {4}, Serial Number: {5}, Firmware: {6}, Slot Number: {7}

Cause: Previously missing hard disk or flash disk of size {4} in slot {7} was found.

Action: Informational message. No action required.

HALRT-20003: {0} status changed to normal. Status: {1}, Manufacturer: {2}, Model Number: {3}, Size: {4}, Serial Number: {5}, Firmware: {6}, Slot Number: {7}

Cause: A hard disk or flash disk of size {4} in slot {7} status changed to normal.

Action: Informational message. No action required.

HALRT-20004: {0} failed. Status: {1}, Manufacturer: {2}, Model Number: {3}, Size: {4}, Serial Number: {5}, Firmware: {6}, Slot Number: {7}

Cause: A hard disk or flash disk of size {4} in slot {7} failed.

Action: The A hard disk or flash disk has failed. A white server locator LED has been lit to help locate the affected database server, and an amber Fault-Service Required LED and a blue OK to Remove LED have both been lit on the drive to help locate the affected drive. Please replace the drive. Detailed information on this problem can be found at https://support.oracle.com/CSP/ma in/article?cmd=show&type=NOT&id=1113034.1 (or hard drives) or https://support.oracle.com/CSP/ma in/article?cmd=show&type=NOT&id=2285526.1 (for flash drives).

HALRT-20005: {0} entered predictive failure status. Status: {1}, Manufacturer: {2}, Model Number: {3}, Size: {4}, Serial Number: {5}, Firmware: {6}, Slot Number: {7}

Cause: A hard disk or flash disk of size {4} in slot {7} entered predictive failure status.

Action: Informational. The hard disk or flash disk has entered predictive failure status. A white server locator LED has been turned on to help locate the affected database server, and an amber Fault-Service Required LED has been lit on the drive to help locate the affected drive. Detailed information on this problem can be found at https://support.oracle.com/CSP/ma in/article?cmd=show&type=NOT&id=1113034.1 (or hard drives) or https://support.oracle.com/CSP/ma in/article?cmd=show&type=NOT&id=2285526.1 (for flash drives).

HALRT-20006: {0} status changed to offline. Status: {1}, Manufacturer: {2}, Model Number: {3}, Size: {4}, Serial Number: {5}, Firmware: {6}, Slot Number: {7}

Cause: {0} of size {4} in slot {7} status changed to offline.

Action: Informational message. No action required.

HALRT-20007: {0} status changed to rebuilding. Status: {1}, Manufacturer: {2}, Model Number: {3}, Size: {4}, Serial Number: {5}, Firmware: {6}, Slot Number: {7}

Cause: {0} of size {4} in slot {7} status changed to rebuilding.

Action: Informational message. The disk is being added back to the RAID5 configuration. A clear alert will be sent once the rebuild is completed.

HALRT-20008: {0} was replaced and entered rebuilding status. Status: {1}, Manufacturer: {2}, Model Number: {3}, Size: {4}, Serial Number: {5}, Firmware: {6}, Slot Number: {7}

Cause: {0} of size {4} in slot {7} replaced and entered rebuilding status.

Action: Informational message. The disk was replaced and is being added back to the RAID5 configuration. A clear alert will be sent once the rebuild is completed.

HALRT-20009: {0} was pushed back and entered rebuilding status. Status: {1}, Manufacturer: {2}, Model Number: {3}, Size: {4}, Serial Number: {5}, Firmware: {6}, Slot Number: {7}

Cause: {0} of size {4} in slot {7} pushed back and entered rebuilding status.

Action: Informational message. The disk was pushed back and is being added back to the RAID5 configuration. A clear alert will be sent once the rebuild is completed.

HALRT-20010: {0} completed rebuilding and changed back to normal. Status: {1}, Manufacturer: {2}, Model Number: {3}, Size: {4}, Serial Number: {5}, Firmware: {6}, Slot Number: {7}

Cause: {0} of size {4} in slot {7} completed rebuilding and changed back to normal.

Action: Informational message. No action required.

HALRT-20011: A disk expansion kit was installed. The additional physical drives were automatically added to the existing RAID5 configuration, and reconstruction of the corresponding virtual drive was automatically started.

Cause: Virtual drive reconstruction due to disk expansion was started.

Action: No action is required. A clear alert will be sent once the virtual drive reconstruction is completed.

HALRT-20012: Virtual drive reconstruction due to disk expansion was completed.

Cause: Virtual drive reconstruction due to disk expansion was completed.

Action: Informational message. No action required.

HALRT-20013: Active physical core count was changed successfully. Reboot the machine to make the change effective.

Cause: Active physical core count was changed.

Action: Reboot the server.

HALRT-20014: The change of active physical core count was applied successfully.

Cause: The change of active physical core count was applied successfully.

Action: Informational message. No action required.

HALRT-20015: Failed to change the active physical core count. {0} active physical cores are expected while {1} physical cores are active.

Cause: Failed to change the active physical core count.

Action: Run the command ALTER DBSERVER PENDINGCORECOUNT={0} to set the active physical core count.

HALRT-20016: Failed to change the active physical core count. {0} active physical cores are expected while {1} physical cores are active.

Cause: Failed to change the active physical core count.

Action: Run the command ALTER DBSERVER PENDINGCORECOUNT={0} FORCE to set the active physical core count.

HALRT-20017: Diagnostic package is attached. It is also accessible at {0}.

Cause: An automatic diagnostic package is available on the database server.

Action: Informational message. No action required.

HALRT-20018: Diagnostic package is accessible at {0}.

Cause: An automatic diagnostic package is available for the database server, but is not attached to the alert message.

Action: Retrieve the diagnostic package from the specified location.

D.17 Oracle Exadata Database Machine Command-Line Interface Error Messages

The following categories of Oracle Exadata Database Machine error messages are described in this section:

D.17.1 Error Messages: DBM-00001 to DBM-00500

These messages are in the range DBM-00001 through DBM-00500.

DBM-00050: SNMP V3 ASR subscriptions must specify an snmpUser directive with authProtocol SHA and privProtocol AES. These are the only protocols supported by ASR.

Cause: The ASR subscription did not specify the directive and protocol.

Action: Correct the snmpUser directive to have the correct protocol values for authProtocol and privProtocol.

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

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

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

Cause: The user definition was already defined.

Action: Define a new user.

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

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

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

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

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

DBM-00059: The snmpSubcriber 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.

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

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

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

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

Cause: An invalid user name was entered.

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

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

DBM-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 created again.

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.

D.17.2 Error Messages: DBM-10001 to DBM-10500

These messages are in the range DBM-10001 through DBM-10500.

DBM-10001: An invalid number was specified for the pendingCoreCount attribute. Specify a valid number for the X4-2 active cores (12, 14, 16, 18, 20, 22, 24).

Cause: An incorrect number was specified for the pending cores.

Action: Enter the command using a valid number.

DBM-10002: An invalid number was specified for the pendingCoreCount attribute. Specify a valid number for the X4-8 active cores (64, 72, 80, 88, 96, 104, 112, 120).

Cause: An incorrect number was specified for the pending cores.

Action: Enter the command using a valid number.

DBM-10003: An invalid number was specified for the pendingCoreCount attribute. Specify a valid number for the X5-2 active cores (12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32, 34, 36).

Cause: An incorrect number was specified for the pending cores.

Action: Enter the command using a valid number.

DBM-10004: Decreasing the number of active cores is not supported.

Cause: The specified number for active cores is less than the existing number of active cores.

Action: Re-enter the command using a larger number.

DBM-10005: Failed to change the number of active cores.

Cause: The number of active cores was not changed.

Action: Retry the command. If the command fails again, then contact Oracle Support Services.

DBM-10006: The pendingCoreCount can only be modified on X3-2, X4-2, X4-8, X5-2, X6-2, X7-2, X7-8 or X5-8.

Cause: The activeCoreCount attribute was not available for this rack.

Action: Capacity-on-Demand is supported on Oracle Exadata Database Machine X3-2 and later systems.

DBM-10007: Cannot modify the pendingCoreCount attribute because iassMode is on.

Cause: The attribute was not modified because iassMode was set to on.

Action: Set the iaasMode attribute to off, and then modify the pendingCoreCount attribute.

DBM-10008: An invalid setting was specified for the iaasReason attribute. Specify a valid setting (expansion, test, HA).

Cause: An invalid setting was specified.

Action: Enter the command using a valid setting. Valid settings are expansion, test, and HA.

DBM-10009: The attribute {0} can only be modified on X3-2, X3-8, X4-2, X4-8, X5-2, X5-8 or X6-2.

Cause: The attribute was not available for this rack.

Action: IaaS (Infrastructure as a Service) is supported on Oracle Exadata Database Machine X3-2 to X6-2 systems.

DBM-10010: Failed to enable IaaS.

Cause: IaaS was not enabled due to an error.

Action: Correct the error and then re-enter the command.

DBM-10011: Failed to disable IaaS.

Cause: IaaS was not disabled due to an error.

Action: Correct the error and then re-enter the command.

DBM-10012: IaaS setting cannot be changed because not all cores are active.

Cause: Not all physical cores are active.

Action: The iaasMode attribute can only be turned on when all physical cores are active. Activate the cores, and then set the attribute.

DBM-10013: The iaasReason attribute can only be changed when setting the iaasIdleInUse attribute to TRUE.

Cause: The iaasReason attribute could not be changed.

Action: The iaasReason attribute is set when setting the iaasIdleInUse attribute is being set to true. To change the iaasReason attribute, disable the iaasIdleInUse attribute, and then re-enable it with a different iaasReason attribute.

DBM-10014: The iaasReason attribute must be specified to set iaasIdleInUse to true.

Cause: The iaasReason attribute was not specified when setting the iaasIdleInUse attribute.

Action: Enter the command with the iaasReason attribute. Valid settings are expansion, test, and HA.

DBM-10015: IaaS setting cannot be changed because BIOS and ILOM are out of sync. Reboot the system and run the command again.

Cause: The BIOS and ILOM are out of synchronization.

Action: Restart the system, and run the command.

DBM-10016: IaaS is not enabled. No need to specify a setting for the attribute iaasReason.

Cause: The iaasReason attribute did not need to be specified because IaaS was not enabled for the system.

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

DBM-10017: The iaasIdleInUse attribute cannot be modified because iaasMode is not on.

Cause: The attribute was not modified because the iaasMode attribute was not set to on.

Action: Set the iaasMode attribute to on, and then set the iaasIdleInUse attribute.

DBM-10018: An invalid setting was specified for the iaasMode attribute. Specify a valid setting (on, off).

Cause: An invalid setting was specified for the attribute.

Action: Enter the command with the iaasReason attribute. Valid settings are ON, and OFF.

DBM-10019: Failed to change the iaasMode attribute.

Cause: The iaasIdleInUse attribute was not changed due to an error.

Action: Correct the error and retry the command.

DBM-10020: Cannot modify the iaasMode attribute and the pendingCoreCount attribute at the same time.

Cause: The attributes were specified at the same time.

Action: Modify each attribute using separate commands.

DBM-10021: IaaS is not supported on virtual machines.

Cause: You attempted to enable IaaS on a virtual machine.

Action: Connect to a bare metal server and retry the command.

DBM-10022: At least {0} physical cores need to be active in order to support IaaS.

Cause: You attempted to enable IaaS on a machine with less than the required number of active cores.

Action: Activate the cores, and then enable IaaS.

DBM-10023: An invalid number was specified for the pendingCoreCount attribute. Specify a valid number for the X5-8 active cores (72, 80, 88, 96, 104, 112, 120, 128, 136, 144).

Cause: An incorrect number was specified for the pending cores.

Action: Retry the command using a valid number.

DBM-10024: ALTER LUN REENABLE command is not supported on compute servers.

Cause: You entered the ALTER LUN REENABLE command on a database serer.

Action: Connect to a storage server and retry the command.

DBM-10025: ALTER PHYSICALDISK DROP FOR REPLACEMENT command is not supported on compute servers.

Cause: You entered the ALTER PHYSICALDISK DROP FOR REPLACEMENT command on a database serer.

Action: Connect to a storage server and retry the command.

DBM-10026: An invalid number was specified for the pendingCoreCount attribute. Specify a valid number for the X3-2 active cores (8, 12, 16).

Cause: An incorrect number was specified for the pending cores.

Action: Retry the command using a valid number.

DBM-10027: Cannot modify the {0} attribute because the server model retrieved from the system is in valid. Contact Oracle Support Services.

Cause: The server configuration contains an invalid server model value.

Action: Contact Oracle Support Services.

DBM-10028: An invalid number was specified for the pendingCoreCount attribute. Specify a valid number for the X6-2 active cores (8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32, 34, 36, 38, 40, 42, 44).

Cause: An incorrect number was specified for the pending cores.

Action: Retry the command using a valid number.

DBM-10030: An invalid number was specified for the pendingCoreCount attribute. Specify a valid number for the X7-2 active cores (8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32, 34, 36, 38, 40, 42, 44, 46, 48).

Cause: An incorrect number was specified for the pending cores.

Action: Retry the command using a valid number.

DBM-10031: An invalid number was specified for the pendingCoreCount attribute. Specify a valid number for the X7-8 active cores (56, 64, 72, 80, 88, 96, 104, 112, 120, 128, 136, 144, 152, 160, 168, 176, 184, 192).

Cause: An incorrect number was specified for the pending cores.

Action: Retry the command using a valid number.

DBM-10032: An invalid number was specified for the pendingCoreCount attribute. Specify a valid number between {0} and {1} which is a multiple of {0}.

Cause: An incorrect number was specified for the pending cores.

Action: Retry the command using a valid number.

DBM-10033: The {0} attribute cannot be modified on eighth rack.

Cause: You attempted to modify an attribute that is not supported on Eighth Rack servers.

Action: Informational.

D.18 Contacting Oracle Support Services

Some error messages or alerts 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 Oracle Auto Service Request (ASR). 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.1.0.

  • 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 will also be expected to provide the following:

  • Your name

  • The name of your organization

  • Your Oracle Support ID number

  • Your telephone number

  • Rack master serial number