Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-1642953.1
Update Date:2016-04-10
Keywords:

Solution Type  Technical Instruction Sure

Solution  1642953.1 :   Griddisks in Status SYNCING after activating griddisks or after cell node restart  


Related Items
  • Exadata X3-2 Hardware
  •  
  • Oracle Platinum Services
  •  
Related Categories
  • PLA-Support>Eng Systems>Exadata/ODA/SSC>Oracle Exadata>DB: Exadata_EST
  •  




Created from <SR 3-8796197827>

Applies to:

Exadata X3-2 Hardware - Version All Versions and later
Oracle Platinum Services - Version N/A to N/A
Information in this document applies to any platform.

Goal

On a Exadata storage cell, Customer would like to know if the current sync time is normal, or if there is an issue. The sync operation has been going on for few hours.

Resync will occur only if the griddisks were made offline and online by alter griddisk all inactive/active and rebooting the cell node etc. If the Disk gets replaced, It will perform a rebalance.


# cellcli -e list griddisk attributes name, asmmodestatus
  DATA_DM05_CD_00_dm05cel01 SYNCING
  DATA_DM05_CD_01_dm05cel01 SYNCING
  DATA_DM05_CD_02_dm05cel01 SYNCING
  DATA_DM05_CD_03_dm05cel01 SYNCING
  DATA_DM05_CD_04_dm05cel01 SYNCING
  DATA_DM05_CD_05_dm05cel01 SYNCING
  DATA_DM05_CD_06_dm05cel01 SYNCING
  DATA_DM05_CD_07_dm05cel01 SYNCING
  DATA_DM05_CD_08_dm05cel01 SYNCING
  DATA_DM05_CD_09_dm05cel01 SYNCING
  DATA_DM05_CD_10_dm05cel01 SYNCING
  DATA_DM05_CD_11_dm05cel01 SYNCING
  DBFS_DG_CD_02_dm05cel01 ONLINE
  DBFS_DG_CD_03_dm05cel01 ONLINE
  DBFS_DG_CD_04_dm05cel01 ONLINE
  DBFS_DG_CD_05_dm05cel01 ONLINE
  DBFS_DG_CD_06_dm05cel01 ONLINE
  DBFS_DG_CD_07_dm05cel01 ONLINE
  DBFS_DG_CD_08_dm05cel01 ONLINE
  DBFS_DG_CD_09_dm05cel01 ONLINE
  DBFS_DG_CD_10_dm05cel01 ONLINE
  DBFS_DG_CD_11_dm05cel01 ONLINE
  RECO_DM05_CD_00_dm05cel01 ONLINE
  RECO_DM05_CD_01_dm05cel01 ONLINE
  RECO_DM05_CD_02_dm05cel01 ONLINE
  RECO_DM05_CD_03_dm05cel01 ONLINE
  RECO_DM05_CD_04_dm05cel01 ONLINE
  RECO_DM05_CD_05_dm05cel01 ONLINE
  RECO_DM05_CD_06_dm05cel01 ONLINE
  RECO_DM05_CD_07_dm05cel01 ONLINE
  RECO_DM05_CD_08_dm05cel01 ONLINE
  RECO_DM05_CD_09_dm05cel01 ONLINE
  RECO_DM05_CD_10_dm05cel01 ONLINE
  RECO_DM05_CD_11_dm05cel01 ONLINE
 

Solution

Verify Grid Infrastructure is on version 11.2.0.3 or above.

1)
Go on to the DB Nodes and go to the ASM trace directory

Example,

cd /u01/app/oracle/diag/asm/+asm/trace/

2)
Do a ls -ltr *s0*

Do this on ALL the ASM Instance trace directories, the file updated last is the process doing the resync.

3)
Do a tail -f of that file and see if is getting updated.

if it does, RESYNC is moving along, as in 11.2.0.3 the disk resync is done by the sxxx slave Process.

This process can take some time depending on how busy the machine is, and if it has been while this individual server was down for repair.

Note:

This RESYNC operation is not a rebalance managed by ARBX.

This operation uses Fast Mirror Resync operation - which does not trigger an ASM rebalance. The Resync operation restores only the extents that would have been written while the disk was offline.

Disk resync is run by one single process. It is not possible to increase the speed of RESYNC or add more slaves.

 

References

<NOTE:1274322.1> - Oracle Sun Database Machine X2-2/X2-8 , X3-2/X3-8 and X4-2 High Availability Best Practices

Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback