Exadata Database Machine V2
 
Oracle Exadata Hardware
 

PLA-Support>Database Technology>Engineered Systems>Oracle Exadata>DB: Exadata_EST
 
.Old GCS Categories>ST>Server>Engineered Systems>Exadata>Generic Errors (ORA-600,ORA-7445,etc)
 

A Disk Failure or Disk going offline during a re size operation may result  ORA-00600: internal error code, arguments: [17090] and failure of re-size operation

Applies to:

Symptoms

A Disk Failure or Disk going offline during a re size operation may result  ORA-00600: internal error code, arguments: [17090] and failure of re-size operation.

Cause

This is  due to Bug 9847699

Solution

When this bug hit an ORA-00600 [17090] is reported and resize operation fails. In exadata, if this happens due to a disk failure during  the resize following action may be taken.

1. Re-issue the failed disk resize command.

    ALTER DISKGROUP <DG_NAME> RESIZE ALL SIZE <NEW_SIZE> REBALANCE POWER <N>;

2. Wait for Rebalance to Finish .

3. Replace the   failed disk , following the  procedure appropriate for the version.

(DISK resize procedure in  Exadata Involves   resize of  grid disks first and then resize of disks at ASM level. If the failed disk is replaced before the  ASM Disk resize completes it may get added to ASM with new (in most cases bigger  ) size and in certain cases it may lead to space issues during rebalance. Hnece it is safe to complete the resize operation first and then replace the failed disk).

This bug will be fixed in version 12.1

References

This solution has no attachment