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 has
CRS-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.
Correct answer is B
http://docs.oracle.com/cd/E16655_01/server.121/e17636/restart.htm#ADMIN12708
About Startup Dependencies
Oracle Restart ensures that Oracle components are started in the proper order, in accordance with component dependencies. For example, if database files are stored in Oracle ASM disk groups, then before starting the database instance, Oracle Restart ensures that the Oracle ASM instance is started and the required disk groups are mounted. Likewise, if a component must be shut down, Oracle Restart ensures that dependent components are cleanly shut down first.
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.
B – TRUE
j/w
B
B is right answer
B
Previously, 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).
Answer is : A
• 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.
From
So B should be correct
It looks that the correct answer is (B).
Not A because in the below process the instance is try to start the SQL * Plus utility. If we start the instance with SQL * PLUS no depend objects like Listeners or ASM disk group comes up.
“When you start an instance on a high with SQL *Plus dependent listeners and ASM disk groups are automatically started.”
Correct Answer is B and not A
——————————————————————————–
Name Target State Server State details
——————————————————————————–
Local Resources
——————————————————————————–
ora.DATA.dg
OFFLINE OFFLINE STABLE
ora.LISTENER.lsnr
OFFLINE OFFLINE STABLE
ora.asm
OFFLINE OFFLINE Instance Shutdown,ST
ABLE
ora.ons
OFFLINE OFFLINE STABLE
——————————————————————————–
Cluster Resources
——————————————————————————–
ora.cssd
1 ONLINE ONLINE STABLE
ora.diskmon
1 OFFLINE OFFLINE STABLE
ora.evmd
1 ONLINE ONLINE STABLE
ora.orcl.db
1 OFFLINE OFFLINE Instance Shutdown,ST
ABLE
——————————————————————————–
SQL> startup;
ORA-01078: failure in processing system parameters
ORA-01565: error in identifying file ‘+DATA/orcl/spfileorcl.ora’
ORA-17503: ksfdopn:2 Failed to open file +DATA/orcl/spfileorcl.ora
ORA-15077: could not locate ASM instance serving a required diskgroup
Answer is B :
http://docs.oracle.com/database/121/ADMIN/restart.htm#ADMIN12710
About Startup Dependencies
Oracle Restart ensures that Oracle components are started in the proper order, in accordance with component dependencies. For example, if database files are stored in Oracle ASM disk groups, then before starting the database instance, Oracle Restart ensures that the Oracle ASM instance is started and the required disk groups are mounted. Likewise, if a component must be shut down, Oracle Restart ensures that dependent components are cleanly shut down first.
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:
CRS-4622: Oracle High Availability Services auto start is enabled.
This simply implies that autostart has been enabled. Autostart will start listeners and ASM groups when the instance is started.
Grid Infrastructure may also do other options, but this message only refers to the autostart feature being enabled.
B see last paragraph below…
Oracle utilities such as SQL*Plus, the Listener Control utility (LSNRCTL), and ASMCMD are integrated with Oracle Restart. If you shut down the database with SQL*Plus, Oracle Restart does not interpret this as a database failure and does not attempt to restart the database. Similarly, if you shut down the Oracle ASM instance with SQL*Plus or ASMCMD, Oracle Restart does not attempt to restart it.
An important difference between starting a component with SRVCTL and starting it with SQL*Plus (or another utility) is the following:
When you start a component with SRVCTL, any components on which this component depends are automatically started first, and in the proper order.
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.
B