Step 3: Enable and Verify the New Disk Controller BBU

1.9.1.3 Step 3: Enable and Verify the New Disk Controller BBU

Similar to Step 1: Prepare the Disk Controller BBU for Removal, this step has two subsections:

For Systems with Remote Mount BBU

For systems with remote mount BBU, the system was not shut down at the end of Step 1: Prepare the Disk Controller BBU for Removal.

If you are using Oracle Exadata System Software version 11.2.3.3.0 or later:

Note:

If you are running Oracle Exadata System Software 19.1.0 or later, substitute /opt/MegaRAID/storcli/storcli64 for /opt/MegaRAID/MegaCli/MegaCli64 in the following commands:

Log in as the root user.
Verify the disk controller BBU battery state is present and seen by the RAID controller. It may take several minutes for the new BBU battery to be detected.

Note:
If you are running on Solaris, use /opt/MegaRAID/MegaCli in place of /opt/MegaRAID/MegaCli/MegaCli64 in the commands below.
```
# /opt/MegaRAID/MegaCli/MegaCli64 -AdpAllInfo -a0 | grep BBU
BBU : Present
BBU : Yes
Cache When BBU Bad : Disabled
```
Re-enable the disk controller BBU and disk cache.
- If you are running Oracle Exadata System Software version 12.1.2.1.0 or later:
```
DBMCLI> ALTER DBSERVER BBU REENABLE
```
- If you are running Oracle Exadata System Software version earlier than 12.1.2.1.0:
```
# /opt/oracle.cellos/compmon/exadata_mon_hw_asr.pl -reenable_bbu
HDD disk controller battery has been reenabled.
```
Verify the disk controller BBU battery state is operational.
- If you are running Oracle Exadata System Software version 12.1.2.1.0 or later:
```
DBMCLI> LIST DBSERVER ATTRIBUTES bbustatus
```
- If you are running Oracle Exadata System Software version earlier than 12.1.2.1.0:
```
# /opt/oracle.cellos/compmon/exadata_mon_hw_asr.pl -list_bbu_status
BBU status: present
```

Verify the current logical disk drive cache policy uses writeback mode:

# /opt/MegaRAID/MegaCli/MegaCli64 -ldpdinfo -a0 | grep -i bbu
Default Cache Policy: WriteBack, ReadAheadNone, Direct, No Write Cache if Bad BBU
Current Cache Policy: WriteBack, ReadAheadNone, Direct, No Write Cache if Bad BBU
... <repeated for each logical volume present>

If the current cache policy is WriteThrough mode, and not WriteBack, then check the status of the battery.

# /opt/MegaRAID/MegaCli/MegaCli64 -adpbbucmd -getbbustatus -a0|grep Battery
BatteryType: iBBU08
Battery State : Operational
Battery Pack Missing : No
Battery Replacement required : No

If the "Battery State" is anything other than "Operational" or "Optimal" (exact term depends on image version), investigate and correct the problem before continuing.

The following shows which image version uses "Optimal" and "Operational".

Exadata image version       Battery State         Raid f/w version
---------------------       -------------------   -----------------
 X4    12.1.2.1.0            Optimal              12.12.0-0178
 X4    12.1.1.1.1            Optimal              12.12.0-0178
 X3    11.2.3.3.0            Optimal              12.12.0-0178
 X3    11.2.3.2.2            Optimal              12.12.0-0178
 X3    11.2.3.2.1            Operational          12.12.0-0140

If you are using image version 11.2.3.2.x:

Turn off the server's locate LED.

# ipmitool chassis identify off
Chassis identify interval: off

Wait approximately 5 minutes for the HBA to recognize and start communicating with the new BBU.
Verify the HBA battery status is Operational and charging.
```
# /opt/MegaRAID/MegaCli/MegaCli64 -adpbbucmd -a0
```
Set all logical drives cache policy to WriteBack cache mode.
```
# /opt/MegaRAID/MegaCli/MegaCli64 -ldsetprop wb -lall -a0
```

Verify the current cache policy for all logical drives is now using WriteBack cache mode.

# /opt/MegaRAID/MegaCli/MegaCli64 -ldpdinfo -a0 | grep -i bbu
Default Cache Policy: WriteBack, ReadAheadNone, Direct, No Write Cache if Bad BBU
Current Cache Policy: WriteBack, ReadAheadNone, Direct, No Write Cache if Bad BBU
... <repeated for each logical volume present>

For Systems That Do Not Have a Remote Mount BBU

For systems that do not have a remote mount BBU, you shut down the system at the end of Step 1: Prepare the Disk Controller BBU for Removal. In this section you restart the system and enable the new BBU.

Note:

If you are running Oracle Exadata System Software 19.1.0 or later, substitute /opt/MegaRAID/storcli/storcli64 for /opt/MegaRAID/MegaCli/MegaCli64 in the following commands:

Power on the server by pressing the power button.
After ILOM has booted, power on the server by pressing the power button, and then connect to the server's console.
To connect to the console from the ILOM Web browser (preferred): Access the "Remote Control -> Redirection" tab and click the "Launch Remote Console" button. On ILOM 3.1.x systems, the console button can be launched from the initial Summary Information screen.

To connect to the console from the ILOM CLI:
```
> start /SP/console
```
From the server's console, monitor the system booting. Watch in particular the LSI controller BIOS while it is loading. If it gives a warning message regarding drives with preserved cache, then choose "D" to discard the cache and continue. This is not an issue as the disk will get re-synced after boot by ASM. If it gives a warning message regarding drives are in write-through mode due to a low battery, then choose to continue.
The Exadata boot should continue normally after that, showing the Exadata boot splash screen and continue with normal OS boot messages. Note that there may be a long pause between screen outputs on the ILOM serial console during subsequent boot steps as the default console is the graphics, and the Exadata boot splash screen will not display.
Once full boot is completed, log in as the root user and verify the new battery is seen and is charging.
```
# /opt/MegaRAID/MegaCli/MegaCli64 -adpbbucmd -a0
```
Set all logical drives cache policy to WriteBack cache mode using the battery.
```
# /opt/MegaRAID/MegaCli/MegaCli64 -ldsetprop wb -lall -a0
```
Verify the current cache policy for all logical drives is now using WriteBack cache mode.
```
# /opt/MegaRAID/MegaCli/MegaCli64 -ldpdinfo -a0 | grep BBU
```

Verify the database services were started automatically.

Verify that CRS is running.

# . oraenv
ORACLE_SID = [root] ? +ASM1
The Oracle base for ORACLE_HOME=/u01/app/11.2.0/grid is /u01/app/oracle

# crsctl check crs
CRS-4638: Oracle High Availability Services is online
CRS-4537: Cluster Ready Services is online
CRS-4529: Cluster Synchronization Services is online
CRS-4533: Event Manager is online

In the above output the 1 of +ASM1 refers to the database node number. For example, for database node #3, the value would be +ASM3.

Validate that instances are running.
```
# ps -ef |grep pmon
```
It should return a record for ASM instance and a record for each database.

Parent topic: Replacing a Disk Controller BBU on a Database Server