Error PRCR-1065 and CRS-2529 can be returned while
stopping the ASM using srvctl command on Grid Infrastructure 11.2 and above as
can be seen in the following.
Reason of Error
The reason for this error is that starting from 11.2 Grid Infrastructure, ASM diskgroups are registered with CRS as a resource. Since these diskgroup resources are dependent on ASM, hence you can’t stop ASM resource without stopping diskgroup resources first; or alternatively you can use “–f” option with "srvctl stop asm" command to stop ASM regardless of its dependent resources (i.e. diskgroups). In this example, ora.CRS.dg and ora.DATA.dg are my diskgroup resources for the diskgroup CRS and DATA which hindered stopping the ASM using srvctl command. In the following you can see the correct method/sequence of stopping the ASM.
[grid@salman1 ~]$ crsctl status res –t
--------------------------------------------------------------------------------
Name Target State
Server State
details
--------------------------------------------------------------------------------
Local Resources
--------------------------------------------------------------------------------
ora.CRS.dg
ONLINE ONLINE
salman1 STABLE
ora.DATA.dg
ONLINE ONLINE
salman1 STABLE
ora.LISTENER.lsnr
ONLINE ONLINE
salman1 STABLE
ora.asm
ONLINE ONLINE
salman1
Started,STABLE
ora.ons
OFFLINE
OFFLINE salman1 STABLE
--------------------------------------------------------------------------------
Cluster Resources
--------------------------------------------------------------------------------
ora.cdb.db
1 OFFLINE OFFLINE Instance Shutdown, STABLE
ora.cssd
1 ONLINE ONLINE
salman1 STABLE
ora.diskmon
1 OFFLINE OFFLINE STABLE
ora.evmd
1 ONLINE ONLINE
salman1 STABLE
--------------------------------------------------------------------------------
[grid@salman1 ~]$ srvctl stop asm
PRCR-1065 : Failed to stop resource
ora.asm
CRS-2529: Unable to act on 'ora.asm'
because that would require stopping or relocating 'ora.CRS.dg', but the force
option was not specified
|
Now you will see that if we stop diskgroup
resources before stopping the ASM, there will be no error while stopping ASM
later.
[grid@salman1 ~]$ srvctl stop diskgroup -g crs
[grid@salman1 ~]$ srvctl stop diskgroup -g data
[grid@salman1 ~]$ srvctl stop asm
[grid@salman1 ~]$ crsctl stat res -t
--------------------------------------------------------------------------------
Name Target State
Server State details
--------------------------------------------------------------------------------
Local Resources
--------------------------------------------------------------------------------
ora.CRS.dg
OFFLINE
OFFLINE salman1 STABLE
ora.DATA.dg
OFFLINE OFFLINE salman1 STABLE
ora.LISTENER.lsnr
ONLINE ONLINE
salman1 STABLE
ora.asm
OFFLINE OFFLINE salman1 Instance Shutdown,ST
ABLE
ora.ons
OFFLINE
OFFLINE salman1 STABLE
--------------------------------------------------------------------------------
Cluster Resources
--------------------------------------------------------------------------------
ora.cdb.db
1 OFFLINE OFFLINE Instance
Shutdown,ST
ABLE
ora.cssd
1 ONLINE ONLINE
salman1 STABLE
ora.diskmon
1 OFFLINE OFFLINE STABLE
ora.evmd
1 ONLINE ONLINE
salman1 STABLE
--------------------------------------------------------------------------------
[grid@salman1 ~]$
|
I had problems stopping AMS. In the end I just used crsctl stop/start crs from root and bingo all solved.
ReplyDelete