HALRT-02010: Data hard disk poor performance status

Asset ID:	1-72-1206014.1
Update Date:	2014-05-27
Keywords:

Solution Type Problem Resolution Sure

Solution 1206014.1 : HALRT-02010: Data hard disk poor performance status

Applies to:

Oracle Exadata Storage Server Software - Version 11.2.1.3.1 to 11.2.3.2.0 [Release 11.2]
Exadata Database Machine X2-2 Full Rack
Information in this document applies to any platform.

Symptoms

Oracle Exadata alerts are generated when a data disk enters in poor performance status.

Cause

The physical drive is in poor performance status.

Impact:

Oracle ASM disks on this physical drive are being dropped.
Performance degradation may occur.

Solution

You may need to replace a physical disk because the disk is in poor performance status.

The poor performance status indicates that the physical disk demonstrates extremely poor performance, and should be replaced at the earliest opportunity. The Oracle ASM disks associated with the grid disks on the physical drive 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 drive dies, then refer to Document 1113013.1HALRT-02003: Data hard disk failure

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

1. To identify the physical disk to be replaced, use the following commands:

CellCLI> LIST PHYSICALDISK WHERE diskType=HardDisk AND status="predictive failure" DETAIL
name: 28:3
deviceId: 19
diskType: HardDisk
enclosureDeviceId: 28
errMediaCount: 0
errOtherCount: 0
foreignState: false
luns: 0_3
makeModel: "SEAGATE ST360057SSUN600G"
physicalFirmware: 0705
physicalInterface: sas
physicalSerial: E07L8E
physicalSize: 558.9109999993816G
slotNumber: 3
status: poor performance

Use the disk slot number shown in the slotNumber attribute to locate the affected disk.

2. Wait until the Oracle ASM disks associated with the grid disks on this physical drive 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.

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

When you remove the disk, you will get an alert. The grid disks and cell disks 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.

Note:
When you replace a physical disk, the disk must be acknowledged by the RAID controller before you can use it. This does not take a long time, but you should use the LIST PHYSICALDISK command to ensure the status is NORMAL.

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

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 GV$ASM_OPERATION.ERROR view to determine if the rebalance operation has failed.

Rebalance operations from multiple disk groups can be done on different Oracle ASM instances in the same cluster if the physical disk being replaced contains ASM disks from multiple disk groups. 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.

References:

Sun Fire™ X4170, X4270, and X4275 Servers Service Manual

Attachments

This solution has no attachment