Exadata: HOLD DISKMON KGZM_FENCE_ENTITY - ASM Unable To Access Cells Due To Cell Fencing
(Doc ID 1610017.1)
Last updated on FEBRUARY 20, 2019
Applies to:Oracle Database - Enterprise Edition - Version 184.108.40.206 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
Following error is seen on 220.127.116.11 old installation DISKMON daemon:
ORA-00600: internal error code, arguments: [kszaddossdev8], 
When trying to perform the downgrade from 18.104.22.168 to 22.214.171.124 (after a failed upgrade on the second node).
The following command run successfully on first node
[node1 ~]# /u01/app/126.96.36.199/grid/crs/install/rootcrs.pl -downgrade -force -oldcrshome /u01/app/188.8.131.52/grid -version 184.108.40.206.0
Successfully downgraded Oracle Clusterware stack on this node
First node has the old ocr backup:
[oracle@node1 cdata]$ ls -lart ocr*
-rw------- 1 root root 133692 Nov 23 14:41 ocr220.127.116.11.0
The downgrade failed on the second node:
[node2 ~]# /u01/app/18.104.22.168/grid/crs/install/rootcrs.pl -downgrade -force -lastnode -oldcrshome /u01/app/22.214.171.124/grid -version 126.96.36.199.0
CRS-2672: Attempting to start 'ora.asm' on '<node2>'
CRS-5017: The resource action "ora.asm start" encountered the following error:
ORA-03113: end-of-file on communication channel
Process ID: 20430
Session ID: 66 Serial number: 1CRS-2674: Start of 'ora.asm' on '<node1>' failed
CRS-4000: Command Start failed, or completed with errors.
Failed to start the Clusterware stack from the lower version
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!