When an ASM instance receives a SHUTDOWN NORMAL command, what command does it
pass on to all database instances that rely on the ASM instances disk groups?
A.
TRANSACTIONAL
B.
IMMEDIATE
C.
ABORT
D.
NORMAL
what command does it pass on to all database instances that rely on the ASM instances disk groups?
When an ASM instance receives a SHUTDOWN NORMAL command, what command does it
pass on to all database instances that rely on the ASM instances disk groups?
Wrong answers?
The following list describes the SHUTDOWN modes and describes the behavior of the ASM instance in each mode.
NORMAL Clause
ASM waits for any in-progress SQL to complete before performing an orderly dismount of all of the disk groups and shutting down the ASM instance. Before the instance is shut down, ASM waits for all of the currently connected users to disconnect from the instance. If any database instances are connected to the ASM instance, then the SHUTDOWN command returns an error and leaves the ASM instance running. NORMAL is the default shutdown mode.
IMMEDIATE or TRANSACTIONAL Clause
ASM waits for any in-progress SQL to complete before performing an orderly dismount of all of the disk groups and shutting down the ASM instance. ASM does not wait for users currently connected to the instance to disconnect. If any database instances are connected to the ASM instance, then the SHUTDOWN command returns an error and leaves the ASM instance running. Because the ASM instance does not contain any transactions, the TRANSACTIONAL mode is the same as the IMMEDIATE mode.
ABORT Clause
The ASM instance immediately shuts down without the orderly dismount of disk groups. This causes recovery to occur upon the next ASM startup. If any database instance is connected to the ASM instance, then the database instance aborts.
Sybex OCP book said:
Shutting down the ASM instance is just as easy. A shutdown immediate, shutdown abort, or just a plain shutdown will do fine. If you execute a normal or immediate shutdown command on an ASM instance, that shutdown will fail if there is any database using that ASM instance. An error will be returned and the ASM instance will stay up. As a result, before you shut down the ASM instance, you will need to shut down all databases using that ASM instance.
You can perform a shutdown abort on the ASM instance. This will cause the ASM instance to shut down immediately and all of the associated databases will be shut down in an inconsistent state. This will require instance recovery when the databases are restarted, which can increase the time it takes to reopen the database. Oracle recommends that you not use the shutdown abort command when stopping an ASM instance.
C is true, because is the unique that can order to close instances databases
D
When an ASM instance receives a SHUTDOWN command, it passes the same option
(NORMAL, IMMEDIATE or TRANSACTIONAL) to all database instances that rely on the
ASM instance for disk group services.
It’s in OCP student guide.
D is correct
NORMAL clause ASM side –> Wait inprogress SQL to database side,
Wait to disconnect all users from database side (either active or idle)
Wait to disconnect Database instance If db instance has already been connected)
Therefore Shutdown Normal clause on ASM instance side is corresponded Shutdown Normal Clause on Database Instance
C is correct
The following are the options for the SHUTDOWN command:
• SHUTDOWN NORMAL: The behavior is the same as with an RDBMS instance. The
default shutdown mode waits for any ongoing operation such as a rebalance
before continuing. If a RDBMS instance is still connected to the ASM instance, the
command will fail. It will also wait for any connected user to disconnect. Mounted
disk groups are all dismounted cleanly.
• SHUTDOWN IMMEDIATE: Ongoing operations are allowed to complete, but
connected users will be disconnected from the ASM instance. Again, any RDBMS
instance still connected to the ASM instance will cause the command to fail with
an error.
• SHUTDOWN ABORT: With this option, the ASM instance aborts, and with it any
connected RDBMS instance
—from Pro Oracle Database 11g RAC on Linux
If you do a normal shutdown of the ASM instance, an error will be returned if any Oracle database is using that ASM instance. Use the shutdown abort command to force the ASM instance to shut down. This will cause all other Oracle databases attached to the ASM instance to be shut down with the equivalent of a shutdown abort command.
—from OCP Administrator Certified Professional
also refer, Oracle 10g Database Administrator II: Backup/recovery & Network Administration page 481
E. None of the above
so option E is missing from the question
The following list describes the SHUTDOWN modes and the behavior of the Oracle ASM instance in each mode.
NORMAL Clause
Oracle ASM waits for any in-progress SQL to complete before performing an orderly dismount of all of the disk groups and shutting down the Oracle ASM instance. Before the instance is shut down, Oracle ASM waits for all of the currently connected users to disconnect from the instance. If any database instances are connected to the Oracle ASM instance, then the SHUTDOWN command returns an error and leaves the Oracle ASM instance running. NORMAL is the default shutdown mode.
IMMEDIATE or TRANSACTIONAL Clause
Oracle ASM waits for any in-progress SQL to complete before performing an orderly dismount of all of the disk groups and shutting down the Oracle ASM instance. Oracle ASM does not wait for users currently connected to the instance to disconnect. If any database instances are connected to the Oracle ASM instance, then the SHUTDOWN command returns an error and leaves the Oracle ASM instance running. Because the Oracle ASM instance does not contain any transactions, the TRANSACTIONAL mode behaves the same as IMMEDIATE mode.
ABORT Clause
The Oracle ASM instance immediately shuts down without the orderly dismount of disk groups. This causes recovery to occur upon the next Oracle ASM startup.
If any database instance is connected to the Oracle ASM instance, then the database instance aborts.
If any Oracle Automatic Storage Management Cluster File System (Oracle ACFS) file systems are currently mounted on Oracle ADVM volumes, those file systems should first be dismounted. Otherwise, applications encounter I/O errors and Oracle ACFS user data and metadata may not be written to storage before the Oracle ASM storage is fenced. For information about dismounting an Oracle ACFS file system, see “Deregistering, Dismounting, and Disabling Volumes and Oracle ACFS File Systems”. For more information about user authentication on Oracle ASM instance, see “Authentication for Accessing Oracle ASM Instances”.
So, looks like one more option missing