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-72-1679796.1
Update Date:2014-11-18
Keywords:

Solution Type  Problem Resolution Sure

Solution  1679796.1 :   ORA-27626: Exadata error: 219 (Capability not supported by Cell) in the asm alert log while rolling upgrading cell servers  


Related Items
  • Exadata Database Machine X2-2 Hardware
  •  
Related Categories
  • PLA-Support>Eng Systems>Exadata/ODA/SSC>Oracle Exadata>DB: Exadata_EST
  •  




Created from <SR 3-8959709471>

Applies to:

Exadata Database Machine X2-2 Hardware - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Symptoms

While performing a rolling upgrade on cell nodes, you may see content similar to this in the ASM alert log:

Errors in file /u01/app/grid/product/11.2.0.4/grid_infra_1/rdbms/log/+asm1_rbal_115692.trc:
ORA-27603: Cell storage I/O error, I/O failed on disk o/192.168.10.100/DBFS_DG_CD_08_exa01cel01 at offset 0 for data length 4096
ORA-27626: Exadata error: 202 (Inappropriate Griddisk state)
WARNING: Read Failed. group:1 disk:31 AU:0 offset:0 size:4096

There doesn't seem to be a problem with the actual transactions.

Cause

This has been presented to development under unpublished Bug 18781327  GRIDDISK SECURTdmITY ERROR MESSAGE DURING PATCHING, which is closed as Not a Bug: 

It can be confirmed from the code or trace that cellsrv marks griddisk as inactive after offline query succeeded.  There is no database impact and this is expected behavior.
 

 

Solution

No action is needed.
 

References

<BUG:18781327> - GRIDDISK SECURTITY ERROR MESSAGE DURING PATCHING

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