Oracle Database Appliance X7-2 HA Hardware
 
Oracle Database Appliance X5-2
 
Oracle Database Appliance X6-2 HA Hardware
 
Oracle Database Appliance X3-2
 
Oracle Database Appliance
 
Oracle Database Appliance X4-2
 

PLA-Support>Sun Systems>Sun_Other>Sun Collections>SN-OTH: x64-CAP VCAP
 

In this Document

Goal

Solution

References

Applies to:

Goal

How to Remove and Replace an ONLINE Shared Storage Disk Drive on an Oracle Database Appliance range of servers.

In some instances, we need to replace a disk that is still online and has not been marked FAILED or PredictiveFail status.
This doc will go through the procedure on how to replace an "ONLINE" disk.
For the different scenarios on when you will need to replace an online disk, refer to Doc ID 1497610.1  Determining when Disks should be replaced on Oracle Database Appliance
 

Solution

DISPATCH INSTRUCTIONS:

Disk drives are CRUs (Customer Replaceable Units) and disk drives should be sent to the site for replacement by the customer.


TIME ESTIMATE: 60 minutes

TASK COMPLEXITY: 0

PROBLEM OVERVIEW:
Steps to remove an onlined hard drive in ODA.

INSTRUCTIONS:
Identify the disk drive that needs replacement. 

Refer to Doc ID 1497610.1  Determining when Disks should be replaced on Oracle Database Appliance

Since the disk is still online, you will need to take special precaution before replacing the disk drive.  Please follow steps 1-7 below:

1. Verify all disks are online (v$asm_disk) and verify DATA and RECO disk group configuration issuing queries on ASM instance

 2. In order to identify the disk that needs to be replaced, issue the following command to turn on the LED on the disk

2b. Verify the USABLE_FILE_MB is sufficient to tolerate a disk failure.  In the example below, you are seeing negative value for USABLE_FILE_MB.  This will need to be resolved before replacing the desired disk.

See DOC ID 1558006.1 for details.

Note: If USABLE_FILE_MB is negative, this means there is not sufficient space in the diskgroup to tolerate a disk failure. This will need to be resolved before replacing the desired disk. See DOC ID 1558006.1 for details.

3. Now you can pull-out the disk that you have identified to be replaced.

From oakcli the disk is now removed:

Note* sometimes the removed disk will simply not show in the list above, this is ok, and you can continue to step 4.

4. Verify alert is received

From the ASM alert.log the IO problem is documented:

The OS message is signaling the IO problem:

5. Verify the disk is not available to asm (v$asm_disk) and verify DATA and RECO disk group configuration

The instances still running:

6. Insert the new hard disk back into the slot.

From oakcli point of view:

7. Verify all disks are online (v$asm_disk) and verify DATA and RECO disk group configuration

 Note: Be aware of Bug 22582818 - ODA TREATS HDD WWID AS A SIGNED NUMBER.  This bug is fixed in 12.1.2.7.0

In the disk names below, if there is a "-" sign in the disk name that was just replaced, the disk cannot be used in ASM, and will need to be replaced again.

Refer to Doc ID 2120302.1 for more details.

from the ASM alert.log

and from OS messages file:

 If the newly replaced disk has older firmware from what the ODA Software is expecting, you will need to update the firmware on this disk. If the disk has newer firmware from the existing disks, this is fine, and the firmware does not need to be downgraded to match existing disks.

To upgrade the disk firmware, use the oakcli update -patch command, for example:

For version 12.1.2.7.0 and above, the command syntax has changed to --storage:

******IMPORTANT******

Updating fiwmare will cause a reboot.

If you cannot take a reboot at this time, please schedule one in the near future to perform the infra update.

This solution has no attachment