Unable To Cleanly Shutdown The CRS stack Using "crsctl stop crs -f" (SYSTEMDG in QUIESCING state)
Last updated on NOVEMBER 07, 2017
Applies to:Oracle Database - Enterprise Edition - Version 188.8.131.52 to 184.108.40.206 [Release 11.2]
Information in this document applies to any platform.
Checked Currency on 18-Oct-2014
1) Unable to cleanly shutdown the CRS using any of the next commands:
It failed with the next errors:
CRS-2678: 'ora.crsd' on 'node1' has experienced an unrecoverable failure
CRS-0267: Human intervention required to resume its availability.
CRS-2795: Shutdown of Oracle High Availability Services-managed resources on 'node1' has failed
CRS-4687: Shutdown command has completed with error(s).
CRS-4000: Command Stop failed, or completed with errors.
2) This leaves the SYSTEMDG diskgroup in QUIESCING state (HTML report from <Document 470211.1> ):
3 SYSTEMDG QUIESCING NORMAL 894240 892024 0
0 RECO DISMOUNTED 0 0 0
0 DATA DISMOUNTED 0 0 0
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms