Which two statements are true regarding the attributes of RACDB?

Examine the following output:
[oracIe@gr5153 ~]$ sudo crsctl config crs
CRS-4622: Oracle High Availability Services autostart is enabled.
[oracIe@gr5153 ~]$ srvctl config database -d RACDB -a
Database unique name: RACDB
Database name: RACDB
Oracle home : /u01/app/oracle/product/l11.2.0/dbhome_1
Oracle user: oracle
Spfile: +DATA/ RACDB /spfileRACDB.ora
Domain:
Start options: open
Stop options: immediate
Database role: PRIMARY
Management policy: AUTOMATIC
Server pools: POOL1
Database instances:
Disk Groups: DATA, FRA
Services:
Database is enabled
Database is policy managed
Oracle Clusterware is started automatically after the system boot. Which two statements are true
regarding the attributes of RACDB?

A.
Oracle Clusterware automatically starts RACDB.

B.
You must manually start RACDB.

C.
Database resource is managed by crsd for high availability and may be automatically restarted
in place if it fails.

D.
Database resource Is not managed by crsd for high availability and needs to be restarted
manually if it fails.

Explanation:
Switch Between the Automatic and Manual Policies
By default, Oracle Clusterware is configured to start the VIP, listener, instance, ASM, database
services, and other resources during system boot. It is possible to modify some resources to have
their profile parameter AUTO_START set to the value 2. This means that after node reboot, or
when Oracle Clusterware is started, resources with AUTO_START=2 need to be started manually
via srvctl. This is designed to assist in troubleshooting and system maintenance. When changing
resource profiles through srvctl, the command tool automatically modifies the profile attributes of
other dependent resources given the current prebuilt dependencies. The command to accomplish
this is:
srvctl modify database -d <dbname> -y AUTOMATIC|MANUAL
D60488GC11
Oracle 11g: RAC and Grid Infrastructure Administration Accelerated 15 3
3.4.1 Benefits of Using Oracle Clusterware
Oracle Clusterware provides the following benefits:
Tolerates and quickly recovers from computer and instance failures.
Simplifies management and support by means of using Oracle Clusterware together with Oracle
Database.
By using fewer vendors and an all Oracle stack you gain better integration compared to using
third-party clusterware.
Performs rolling upgrades for system and hardware changes. For example, you can apply Oracle
Clusterware upgrades, patch sets, and interim patches in a rolling fashion, as follows:
Upgrade Oracle Clusterware from Oracle Database 10g to Oracle Database 11g
Upgrade Oracle Clusterware from Oracle Database release 11.1 to release 11.2
Patch Oracle Clusterware from Oracle Database 11.1.0.6 to 11.1.0.7
Patch Oracle Clusterware from Oracle Database 10.2.0.2 Bundle 1 to Oracle Database 10.2.0.2
Bundle 2
Automatically restarts failed Oracle processes.
Automatically manages the virtual IP (VIP) address so when a node fails then the node’s VIP
address fails over to another node on which the VIP address can accept connections.
Automatically restarts resources from failed nodes on surviving nodes.
Controls Oracle processes as follows:
For Oracle RAC databases, Oracle Clusterware controls all Oracle processes by default.
For Oracle single-instance databases, Oracle Clusterware allows you to configure the Oracle
processes into a resource group that is under the control of Oracle Clusterware.
Provides an application programming interface (API) for Oracle and non-Oracle applications that
enables you to control other Oracle processes with Oracle Clusterware, such as restart or react to

failures and certain rules.
Manages node membership and prevents split-brain syndrome in which two or more instances
attempt to control the database.
Provides the ability to perform rolling release upgrades of Oracle Clusterware, with no downtime
for applications.
Oracle Database High Availability Overview
11g Release 2 (11.2)