Reclaiming the hotspare after upgrading to 184.108.40.206.0 or later
Last updated on FEBRUARY 15, 2016
Applies to:Oracle Exadata Storage Server Software - Version 220.127.116.11.2 and later
This document describes how to manually add the hotspare to the RAID 5 when reclaimdisk.sh cannot do it (starting 18.104.22.168.0). For Exadata releases earlier than 22.214.171.124.0 <Document 1582139.1> needs to be followed.
Systems freshly imaged to Exadata release 126.96.36.199.0 will not have a hotspare. For those cases reclaimdisk will be used to reclaim diskspace from the volume group when choosing either Oracle VM or Oracle Linux 6 on the database server - reclaim will happen within the same RAID5 configuration of 4 (or 8) disks. For systems upgraded to 188.8.131.52.0 that previously had a hotspare, reclaimdisk.sh cannot be used to reclaim diskspace from the hotspare. As shown in the example below reclaimdisk will not work to reclaim the hotspare in release 184.108.40.206.0.
In this process the database server will be rebooted twice. It is assumed the Grid Infrastructre is disabled to start after node boot-up.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms