Oracle Database Appliance
 

PLA-Support>Sun Systems>x86>Engineered Systems HW>SN-x64: ORA-DATA-APP
 

After replace disks on ODA, the new disk name has "-" in it for example: HDD_E1_S19_-1925008273
OS can see it but the name with character "-" prevent the disk add into ASM because of ASM limitation.

In this Document

Symptoms

Changes

Cause

Solution

References

Applies to:

Symptoms

After a disk replacement in ODA, the new disk name has "-" in front of it, example: HDD_E1_S19_-XXXXXXX

The related disk cannot be add into ASM.

Changes

Replace a shared disk, this does not affect the internal OS drives.

Cause

In  ODA, the OAK daemon generates a system-unique disk ID from a combination of device type, SCSI expander number, disk shelf slot number, a unique disk ID and the partition number. The disk ID is derived from the device’s World Wide Name (WWN) or World Wide Identifier (WWID). (For purposes of this discussion “WWN” and “WWID” may be used interchangeably.)

The WWN is a 64-bit number. It may be read electronically and is also printed on the physical drive label as a 16-digit hexadecimal number. Oakd masks the low order 32 bits (8 digits) and converts to decimal to produce the disk ID.

So the disk WWN  on the disk package has 16 digital like 5000CCA0(1)FDDD8C0  --- the 9th digit from left 8th from right at this case is 1.

If this digit is >7, the derived device name used by ASM will have a "-" in it, and cannot be used by ASM.

If the digit is <=7, it will be fine.


oakd (prior to OAK version 12.1.2.7.0) treats the disk ID as a 32-bit signed number. Bit 31 is the sign bit – if it is 1, the disk ID is converted as a negative number.

 
V1 ODA, HDD, slot 19, WWN 5000c5008d42b46f
Unsigned:
Disk ID = 0x8d42b46f = 2369959023
ODA disk name  = HDD_E1_S19_2369959023
Signed:
Disk ID = 0x8d42b46f = -1925008273
ODA disk name  = HDD_E1_S19_-1925008273

The “-“ character is invalid as an ASM disk name, so attempts to bring the disk online fail.

This is will fix in 12.1.2.7.0

Solution

The only workaround is the replace the disk with another disk with the right wwid again.  Usually we can ship another disk for replacement but that disk can have wrong wwid also.  So we will need keep on send new disks until the right wwid disk reach customer.  

Please add the SR to this bug, so we can keep track on how many customer's have hit on this issue.

References

This solution has no attachment