Exadata Command "drop for replacement" Fails With CELL-02018

Asset ID:	1-72-2192650.1
Update Date:	2017-11-15
Keywords:

Solution Type Problem Resolution Sure

Solution 2192650.1 : Exadata Command "drop for replacement" Fails With CELL-02018

Applies to:

Exadata X6-2 Hardware - Version All Versions to All Versions [Release All Releases]
Exadata X5-2 Hardware - Version All Versions to All Versions [Release All Releases]
Exadata X3-2 Half Rack - Version All Versions to All Versions [Release All Releases]
Exadata X5-8 Hardware - Version All Versions to All Versions [Release All Releases]
Oracle Exadata Storage Server Software - Version 12.1.1.1.0 and later
Information in this document applies to any platform.

Symptoms

The command ALTER SYSTEM DISK <DISK:ID> DROP FOR REPLACEMENT fails with error "CELL-02018: Internal error detected: null"
Disk has not been removed or replaced.

Cause

There is a disconnect between the physical disk status and the status of the disk in ASM. At the physical level, the disk is not dropped. At the ASM level it is not recognized as being present (e.g. - it is dropped). This can be verified by comparing results of the cellcli commands list physicaldisk detail, list griddisk detail and list celldisk detail.

The list physicaldisk detail command will show "failed" instead of "failed - dropped for replacement". This indicates the disk has not been dropped.

20:11 0_11 FALSE FALSE failed

However, list griddisk detail will show "not present"...

     name: DBFS_DG_CD_11_nc1zp2celadm08
     <SNIP>
     status: not present

...as will list celldisk detail...

     name: CD_11_nc1zp2celadm08
     <SNIP>
     physicalDisk: K7TD8N
     <SNIP>
     status: not present

...indicating ASM thinks the drive is not there.

Solution

1. Physically pull out the disk.

2. Wait between 1 and 2 minutes.

3. Reinsert the disk.

4. Issue the following command:

ALTER PHYSICALDISK <DISK:ID> REENABLE

If this fails, use the FORCE option:

ALTER PHYSICALDISK <DISK:ID> REENABLE FORCE

If the FORCE option fails, go to step 6.

5. Issue the following command:

ALTER SYSTEM DISK <DISK:ID> DROP FOR REPLACEMENT

If the disk drops successfully, stop here as the issue is resolved.

If the disk still does not drop successfully, go on to step 6

6. Collect a Sundiag bundle following Doc ID 1683842.1.

7. Open a Service Request with Oracle Support and upload the Sundiag to the SR.

INTERNAL ONLY

If the above steps have been accomplished and the same symptoms are still occurring (list physicaldisk detail shows "failed" but not "dropped for replacement" and list celldisk detail and list griddisk detail show "not present"), then the drive can be replaced. This is because, as far as ASM is concerned, there is no drive there. Once the new drive is installed, ASM will see and configure it as normal.

References

SR 3-12566521591
SR 3-12858687879
SR 3-12742474246

Attachments

This solution has no attachment