CRS-2974: unable to act on resource
When we tried to stop SCAN for some reason, we got CRS-2974 like this:
[grid@primary01 ~]$ srvctl stop scan
PRCR-1065 : Failed to stop resource ora.scan1.vip
CRS-2974: unable to act on resource 'ora.scan1.vip' on server 'primary02' because that would require stopping or relocating resource 'ora.LISTENER_SCAN1.lsnr' but the appropriate force flag was not specified
PRCR-1065 : Failed to stop resource ora.scan2.vip
CRS-2974: unable to act on resource 'ora.scan2.vip' on server 'primary01' because that would require stopping or relocating resource 'ora.LISTENER_SCAN2.lsnr' but the appropriate force flag was not specified
PRCR-1065 : Failed to stop resource ora.scan3.vip
CRS-2974: unable to act on resource 'ora.scan3.vip' on server 'primary01' because that would require stopping or relocating resource 'ora.LISTENER_SCAN3.lsnr' but the appropriate force flag was not specified
PRCR-1065 : Failed to stop resource ora.scan4.vip
CRS-2974: unable to act on resource 'ora.scan4.vip' on server 'primary02' because that would require stopping or relocating resource 'ora.LISTENER_SCAN4.lsnr' but the appropriate force flag was not specified
CRS-2974 means that SCAN_LISTENER of the cluster still depend on the lives of those SCAN VIP, so you cannot stop SCAN at this moment. In fact, the error warns you that you have to know what you're doing.
Solutions
You can bring SCAN as well as SCAN_LISTENER down at the same time by adding -force option, or in its short form -f.
[grid@primary01 ~]$ srvctl stop scan -f
We forced SCAN VIP to stop as well as SCAN_LISTENER.
Both components will bring back to function.
A softer way to stop those components is to bring SCAN_LISTENER down first, then stop SCAN. Here we takes two steps.
[grid@primary01 ~]$ srvctl stop scan_listener
[grid@primary01 ~]$ srvctl stop scan
I talked more about restart SCAN related components.