Oracle Grid Infrastructure for a stand-alone server is installed on your production host before
installing the Oracle Database server. The database and listener are configured by using Oracle
Restart.
Examine the following command and its output:
$ crsctl config has
CRS-4622: Oracle High Availability Services auto start is enabled.
What does this imply?
A.
When you start an instance on a high with SQL *Plus dependent listeners and ASM disk groups
are automatically started.
B.
When a database instance is started by using the SRVCTL utility and listener startup fails, the
instance is still started.
C.
When a database is created by using SQL* Plus, it is automatically added to the Oracle Restart
configuration.
D.
When you create a database service by modifying the SERVICE_NAMES initialization
parameter, it is automatically added to the Oracle Restart configuration.
Explanation:
Previously (10g and earlier), in the case of Oracle RAC, the CRS took care of the
detection and restarts. If you didn’t use RAC, then this was not an option for you. However, in this
version of Oracle, you do have that ability even if you do not use RAC. The functionality – known
as Oracle Restart – is available in Grid Infrastructure. An agent checks the availability of important
components such as database, listener, ASM, etc. and brings them up automatically if they are
down. The functionality is available out of the box and does not need additional programming
beyond basic configuration. The component that checks the availability and restarts the failed
components is called HAS (High Availability Service).
Here is how you check the availability of HAS itself (from the Grid Infrastructure home):
$ crsctl check hasCRS-4638: Oracle High Availability Services is online
Note:
* crsctl config has
Use the crsctl check has command to display the automatic startup configuration of the Oracle
High Availability Services stack on the server.
* The crsctl config has command returns output similar to the following:
CRS-4622: Oracle High Availability Services autostart is enabled.
it’s B: Oracle Restart also manages the weak dependency between database instances and the Oracle Net listener (the listener): When a database instance is started, Oracle Restart attempts to start the listener. If the listener startup fails, then the database is still started. If the listener later fails, Oracle Restart does not shut down and restart any database instances.
A is wrong: When you start a component with SQL*Plus (or another utility), other components in the dependency chain are not automatically started; you must ensure that any components on which this component depends are started.
see: http://docs.oracle.com/cd/E51608_01/doc/doc.20/e48475/ch2migrasteps.htm#DUMAG322
Yes B is correct.
please refer to:
If the listener later fails,
Oracle Restart does not shut down and restart any database instances.
http://docs.oracle.com/cd/E16655_01/server.121/e17636/restart.htm#ADMIN12710
Just beneath, are a lot of totally not related sites to ours, nonetheless, they are certainly worth going over.
B is correct answer
B