RE: crsctl check resource on Rac

From: Matt <>
Date: Sun, 16 Mar 2014 17:03:16 -0400
Message-ID: <005701cf415b$26de0e70$749a2b50$_at_net>

Martin, Thank You!!

I looked in all the clusterware logs and could find the error when I did the srvctl command and when the database tried to start I did see the error reported in the clusteware logs in crsd.log(If I remember correctly), but did not find a root cause. My ASM logs were purged so I did not have enough history to identify a root cause.

-----Original Message-----
From: [] On Behalf Of Martin Klier Sent: Sunday, March 16, 2014 2:39 PM
Cc: Oracle Freelist
Subject: Re: crsctl check resource on Rac


did you check:

$ORA_CRS_HOME/log/hostname/cssd/ocssd.log (this one is a bit talkative)

If there's a failure in checking something, they should point you to the responsible agent's log file in the same directory structure. The agents usually will log very clearly what happened when a check failed (or at least you can see when it succeeded).

Using crsctl commands on ora.* resources works, but in fact is is (just) not supported. Two years ago, I had a discussion with some Oracle guys from the GI team about this fact, and they said, "it's simply because crsctl can change ora.* services", and they don't want us to do so. To make life for support easier, the whole command is not supported. For operational tasks it's not necessary either, and if MOS says "ok", you can use it and complain if it does not work. If you do on your own, nobody will crucify you, as long as you don't complain about it doing not what you hoped for.

Hope this helps
Martin Klier

Am 13.03.2014 16:55, schrieb
> I had a disk group on a node in a RAC cluster go in the intermediate
> state which prevented srvctl from starting the database because there
> was a dependency on the diskgroup. To resolve the issue I ran a
> crsctl check resource ora.DBFS_DG.dg which resolved the issue and
> then the database was able to start just fine through srvctl.

Usn's IT Blog for Oracle and Linux

performing databases
Your reliability. Our concern.


No virus found in this message.
Checked by AVG -
Version: 2014.0.4336 / Virus Database: 3722/7199 - Release Date: 03/15/14

Received on Sun Mar 16 2014 - 22:03:16 CET

Original text of this message