Subscribe to Posts by Email

Subscriber Count

    700

Disclaimer

All information is offered in good faith and in the hope that it may be of use for educational purpose and for Database community purpose, but is not guaranteed to be correct, up to date or suitable for any particular purpose. db.geeksinsight.com accepts no liability in respect of this information or its use. This site is independent of and does not represent Oracle Corporation in any way. Oracle does not officially sponsor, approve, or endorse this site or its content and if notify any such I am happy to remove. Product and company names mentioned in this website may be the trademarks of their respective owners and published here for informational purpose only. This is my personal blog. The views expressed on these pages are mine and learnt from other blogs and bloggers and to enhance and support the DBA community and this web blog does not represent the thoughts, intentions, plans or strategies of my current employer nor the Oracle and its affiliates or any other companies. And this website does not offer or take profit for providing these content and this is purely non-profit and for educational purpose only. If you see any issues with Content and copy write issues, I am happy to remove if you notify me. Contact Geek DBA Team, via geeksinsights@gmail.com

Pages

RAC: Find when the CRS resource was last started or status changes

Finding the CRS resource last modified or started will be very clumpsy when you look at crsd.log or any other logs.

For that use -v flag in crsctl status resource command where you can find some important details like last server , last changed, last restart, internal status etc.

For example:-

[grid@node1 ~]$ crsctl status resource ora.mydb.test_srv.svc -l 
NAME=ora.mydb.test_srv.svc 
TYPE=ora.service.type 
CARDINALITY_ID=1 
DEGREE_ID=1 
TARGET=OFFLINE 
STATE=OFFLINE   
CARDINALITY_ID=2 
DEGREE_ID=1 
TARGET=ONLINE 
STATE=ONLINE on node1 
[grid@node1 ~]$ crsctl status resource ora.mydb.test_srv.svc -v 
NAME=ora.mydb.test_srv.svc 
TYPE=ora.service.type 
LAST_SERVER=node2 
STATE=OFFLINE 
TARGET=ONLINE 
CARDINALITY_ID=1 
CREATION_SEED=137 
RESTART_COUNT=0 
FAILURE_COUNT=0 
FAILURE_HISTORY= 
ID=ora.mydb.test_srv.svc 1 1 
INCARNATION=5 
LAST_RESTART=08/10/2011 16:32:53 
LAST_STATE_CHANGE=08/10/2011 16:34:03 STATE_DETAILS= 
INTERNAL_STATE=STABLE 

-Thanks
Geek DBA

Comments are closed.