How To Replace an Older 73g ODA V1 SSD (REDO diskgroup) with a 200G SSD if Using 12.1.2.1.0 or Earlier Versions if the Disk is not Automatically Added

Asset ID:	1-71-2185817.1
Update Date:	2018-05-21
Keywords:

Solution Type Technical Instruction Sure

Solution 2185817.1 : How To Replace an Older 73g ODA V1 SSD (REDO diskgroup) with a 200G SSD if Using 12.1.2.1.0 or Earlier Versions if the Disk is not Automatically Added

Applies to:

Oracle Database Appliance - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.
The issues is fixed at ODA 12.1.2.5.0 or later version.

Goal

The ODA V1 system originally only supported 73GB SSD but currently we only ship 200GB SSD for the replacement of the old 73GB SSD.
Does not apply to X3-2 and newer ODA HW types.

After replacing the SSD the expected result would be the following.

oakcli show diskgroup REDO

ASM_DISK PATH DISK STATE STATE_DETAILS

redo_20 /dev/mapper/SSD_E0_S20_805696280p1 pd_20 ONLINE Good
redo_21 /dev/mapper/SSD_E0_S21_805696538p1 pd_21 ONLINE Good
redo_22 /dev/mapper/SSD_E1_S22_1320849460p1 pd_22 ONLINE Good ---> This is the new SSD drive Appears to have already detected the new UsrDevName
redo_23 /dev/mapper/SSD_E1_S23_805696302p1 pd_23 ONLINE Good

If you are not seeing the disk as added ONLINE and good check your ODA version

oakcli show version

For ODA V1 12.1.2.1 or earlier releases new 200GB SSD disks will not be added into the system.
This is because the older ODA versions were released long before the need to ship 200gb replacement disks.

Newer ODA V1 versions will automatically detect and add the 200gb SSD and resize it to match the 73gb REDO SSD size.

This Note can be used to workaround this issue.

Solution

Step 1: Allow the entire SSD to be partitioned (at 100%).

For oak 2.0 to 2.6 nothing needs to be done.
For oak 2.7 to 12.1.2.1:

oakcli disable validation storage

Step 2: Pull out the old SSD and wait at least 10 minutes.

Step 3: Insert the new 200GB disk

Wait at least 5 minutes.

Step 4: enable the disk

oakcli enable validation storage

At this point, the SSD would have been partitioned to the full size, but it will not be added to the ASM diskgroup.

Step 5: Add to the ASM diskgroup manually

For oak 2.0 to 12.1.2.1: Get the device name as follows:

oakcli show disk pd_<slotnum> | grep UsrDevName

Add the disk with the name identified as above:

alter diskgroup /*+ _OAK_AsmCookie */ REDO add disk '/dev/mapper/<UsrDevName>p1' name <UsrDevName>p1 size 73406M; <-- the size may different slightly based on the version. So before you use this command please check the other ASM redo disk size.

Note: If the customer does not following above steps and already added the new 200GB SSD in which will failed to add into system. A new SSD will have to be shipped to replace that one where the above steps where not executed correctly.

You can use the parted command to print partition sizes in sector terms.

New disk:

e.g. #parted -s /dev/mapper/SSD_E0_S21_<UsrDevName> unit s print

Then compare the size with any other existing 73GB disk to confirm they are equal:

e.g. #parted -s /dev/mapper/SSD_E0_S23_805696302 unit s print

Note: ODA V1 disks redo_20 and redo_21 use E0 e.g. SSD_E0_S2*...p1
while ODA V1 disks redo_22 and redo_23 will use E1 e.g. SSD_E1_S2*...p1

# oakcli show diskgroup redo

        ASM_DISK      PATH                                            DISK            STATE           STATE_DETAILS

        redo_20         /dev/mapper/SSD_E0_S20_805650176p1              pd_20           ONLINE          Good
        redo_21         /dev/mapper/SSD_E0_S21_805650588p1              pd_21           ONLINE          Good
        redo_22         /dev/mapper/SSD_E1_S22_805649830p1              pd_22           ONLINE          Good
        redo_23         /dev/mapper/SSD_E1_S23_805650149p1              pd_23           ONLINE          Good

Attachments

This solution has no attachment