ODA Redeployment Fails during Step #18 - Creating ASM Diskgroup REDO

Asset ID:	1-72-2269930.1
Update Date:	2017-07-11
Keywords:

Solution Type Problem Resolution Sure

Solution 2269930.1 : ODA Redeployment Fails during Step #18 - Creating ASM Diskgroup REDO

Applies to:

Oracle Database Appliance - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Symptoms

On : Oracle Database Appliance (12.1.2.10)

Failed to deploy end user bundle on koda1

/opt/oracle/oak/onecmd/tmp/STEPS-0-24-20170504091944.log
INFO : Running /opt/oracle/oak/onecmd/tmp/redodg.sh on oda1-0 as grid. Check log files in /opt/oracle/oak/onecmd/tmp for details
INFO : This is root, will become grid and run: /bin/su grid -c /usr/bin/ssh -l grid oda1-0 /opt/oracle/oak/onecmd/tmp/redodg.sh
INFO : Running on the local node: /bin/su grid -c /opt/oracle/oak/onecmd/tmp/redodg.sh
INFO : Checking for REDO DG creation status
ERROR : Failure in REDO DG creation, check ASM LOG #Step 18#
INFO : Time in CreateASMDiskgroups is 281 seconds.
Exiting...

Changes

Attempting to re-deploy a V1 ODA :

Cause

There are 2 SSDs that have gone into "Write protected" mode:

You can find the information in the OS Messages file:

messages:May 4 11:28:53 oda1-0 kernel: sd 1:0:18:0: [sdap] Add. Sense: Write protected <<< pd_20
messages:May 4 11:28:53 oda1-0 kernel: sd 1:0:18:0: [sdap] Add. Sense: Write protected
messages:May 4 11:28:53 oda1-0 kernel: sd 1:0:18:0: [sdap] Add. Sense: Write protected

messages:May 4 11:28:57 oda1-0 kernel: sd 1:0:5:0: [sdad] Add. Sense: Write protected <<< pd_22
messages:May 4 11:28:57 oda1-0 kernel: sd 1:0:5:0: [sdad] Add. Sense: Write protected
messages:May 4 11:28:57 oda1-0 kernel: sd 1:0:5:0: [sdad] Add. Sense: Write protected

This is indicative of a supercap failures on the SSDs,
This is typical for the V1 SSD 73GB drives, which have been end of life'd, and are now replaced by the 200GB drives.

All most all other diagnostics including ASMCMD, OAKCLI and other collections will not report the source of the problem.
- You must know where to find the supporting information.

Solution

There is no workaround. The solution is to replace the disks and redeploy

References

<BUG:26088085> - ODA: 12.1.2.10 FAILED TO DEPLOY END-USER BUNDLE ON STEP 18 REDO DG CREATION
<BUG:22463739> - OAK DIDN'T SET DISK STATE ACCORDINGLY WHEN ASM OFFLINE THE DISK
<BUG:21300303> - REDO DISMOUNTED DUE TO WRITE ERROR ON SSDS
<BUG:22101092> - COULD NOT ADD A SSD DISK TO REDO DG IN 12.1.2.3.0
<NOTE:1497610.1> - Determining when Disks should be replaced on Oracle Database Appliance
<NOTE:1461219.1> - ODA HW: After SSD replacement, disk shows STATE as UNINITIALIZED and STATE_DETAILS as NewDiskInserted
<NOTE:1409835.1> - ODA (Oracle Database Appliance): Deployment & Cleanup Steps
<NOTE:888888.1> - Oracle Database Appliance - 12.1.2 and 2.X Supported ODA Versions & Known Issues
<NOTE:1600317.1> - ODA How to Alter the DNS Names Post-Deployment Using GridInst.pl and the Oracle Database Appliance onecommand.params File

Attachments

This solution has no attachment