How to : Replace a Hard Drive in an Exadata Storage Server

In my last company, we support a lot of Exadata. unlike with other company the DBA’s job is only limited to DB Node. but with my previous company we DBA’s support everything.. as in everything, since we have access to root of both DB and Storage Cell.

1. Check the Disk having issue.

 
CellCLI> LIST PHYSICALDISK WHERE diskType=HardDisk AND status LIKE ".*failure.*" DETAIL
         name:                   20:3
         deviceId:               21
         diskType:               HardDisk
         enclosureDeviceId:      20
         errMediaCount:          14
         errOtherCount:          0
         luns:                   0_3
         makeModel:              "SEAGATE ST32000SSSUN2.0T"
         physicalFirmware:       061A
         physicalInsertTime:     2014-06-30T14:15:33+00:00
         physicalInterface:      sas
         physicalSerial:         L2KDFT
         physicalSize:           1863.0166854858398G
         slotNumber:             3
         status:                 warning - predictive failure

CellCLI>

Continue reading

Patch 15887843 MERGE REQUEST ON TOP OF 11.2.3.2.0 FOR BUGS 15841041, 15874381

Patching time again..

Patch 15887843 MERGE REQUEST ON TOP OF 11.2.3.2.0 FOR BUGS 15841041, 15874381
Below are the list of bug fixed on this release.

========== Bug fixes or Diagnostics included in this ONEOFF ===========
Bug Fixes:
        11903713:CELL-2628 DURING LOOP TEST OF CELLCLI LIST QUERIES
        14337259:ASM ARB0 HANG ON REBALANCE IO THAT IS NOT ALIGNED IF BLOCK DIRTY IN FLASH CACHE
        14540423:ORA-7445 [__INTEL_NEW_MEMCPY() CAUSED BY INCORRECT MANAGEMENT OF CHAINED ROWS
        14763896:TOO MANY FILE SYSTEM IOS MAY CAUSE CONFINEMENT DETECTION ON SYSTEM DISKS
        14798635:DOM CONFINEMENT TRIGGERED ON PARTNER CELLS WITH NO WORKLOAD
        14823493:DO NOT POWER CYCLE FOR IO HANG ON WRITE BACK FLASHCACHE
        14841379:SAFEFILE NEEDS FSYNC SUPPORT TO COMMIT CHANGES
        15834287:IF CANNOT GET LOCK ON GRIDDISK LIST ON FLASH DISK, DURING IO HANG DONT REBOOT
        14828059:ORA-1578 REPORTED IN SUPERCLUSTER WITH EXADATA

Continue reading

Steps to power down or reboot a cell without affecting ASM

after applying patch on storage cell some of the patch requires that the cell be restarted.
this is my first time to do the rolling restart…. 😀 😀 😀

When performing maintenance on Exadata Cells, it may be necessary to power down or reboot the cell.
If a storage server is to be shut down when one or more databases are running,
then verify that taking the storage server offline will not impact Oracle ASM disk group
and database availability. The ability to take Oracle Exadata Storage Server offline without
affecting database availability depends on the level of Oracle ASM redundancy used on the affected
disk groups, and the current status of disks in other Oracle Exadata Storage Servers that have mirror
copies of data as Oracle Exadata Storage Server to be taken offline.
Continue reading