ORA.CVU 
 New resource (Cluster Verification Utility) is added in 11.2.0.2 

 Unlike the previous resources, the cvu resource is actually cluster aware. It’s the Cluster Verification Utility we all know from installing RAC. Going by the profile (shown below), I conclude that the utility is run through the grid software owner’s scriptagent and has exactly 1 incarnation on the cluster. It is only executed every 6 hours and restarted if it fails. If you like to execute a manual check, simply execute the action script with the command line argument “check”.

 [root@node1 tmp]# crsctl stat res ora.cvu -p
 NAME=ora.cvu
 TYPE=ora.cvu.type
 ACL=owner:grid:rwx,pgrpinstall:rwx,other::r--
 ACTION_FAILURE_TEMPLATE=
 ACTION_SCRIPT=%CRS_HOME%/bin/cvures%CRS_SCRIPT_SUFFIX%
 ACTIVE_PLACEMENT=1
 AGENT_FILENAME=%CRS_HOME%/bin/scriptagent
 AUTO_START=restore
 CARDINALITY=1
 CHECK_INTERVAL=21600
 CHECK_RESULTS=
 CHECK_TIMEOUT=600
 DEFAULT_TEMPLATE=
 DEGREE=1
 DESCRIPTION=Oracle CVU resource
 ENABLED=1
 FAILOVER_DELAY=0
 FAILURE_INTERVAL=0
 FAILURE_THRESHOLD=0
 HOSTING_MEMBERS=
 LOAD=1
 LOGGING_LEVEL=1
 NLS_LANG=
 NOT_RESTARTING_TEMPLATE=
 OFFLINE_CHECK_INTERVAL=0
 PLACEMENT=balanced
 PROFILE_CHANGE_TEMPLATE=
 RESTART_ATTEMPTS=5
 SCRIPT_TIMEOUT=600
 SERVER_POOLS=*
 START_DEPENDENCIES=hard(ora.net1.network)
 START_TIMEOUT=0
 STATE_CHANGE_TEMPLATE=
 STOP_DEPENDENCIES=hard(ora.net1.network)
 STOP_TIMEOUT=0
 TYPE_VERSION=1.1
 UPTIME_THRESHOLD=1h
 USR_ORA_ENV=
 VERSION=11.2.0.2.0The action script $GRID_HOME/bin/cvures implements the usual callbacks required by scriptagent: start(), stop(), check(), clean(), abort(). All log information goes into $GRID_HOME/log/`hostname -s`/cvu.

 The actual check performed is this one: $GRID_HOME/bin/cluvfy comp health -_format & > /dev/null 2>&1

 [oracle@test-server1]~% srvctl config cvu
 CVU is configured to run once every 360 minutes

 [oracle@test-server1]~% srvctl status cvu
 CVU is enabled and running on node test-server1

 CVU is nothing but cluster verification utility which now would run once every 6 hours(This is configurable and can be changed using srvctl modify). You can see the logs under $GRID_HOME/log/`hostname -s`/cvu

so If its status shows as offline, then no need to wory about. Cluster verification utility get interacted with this resource to get you the results of cvu. If you are not running RAN CLUVFY then its OK..

zhuanzai :http://blog.csdn.net/wonder_2012/article/details/9342241

CVU介绍