Oracle 1z0-053 Exam Practice Questions (P. 4)

Which initialization parameter in an ASM instance specifies the disk groups to be automatically mounted at instance startup?

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?

When starting up your ASM instance, you receive the following error:
SQL> startup pfile=$ORACLE_HOME/dbs/init+ASM.ora

ASM instance started -
Total System Global Area 104611840 bytes

Fixed Size 1298220 bytes -

Variable Size 78147796 bytes -

ASM Cache 25165824 bytes -
ORA-15032: not all alternations performed
ORA-15063: ASM discovered an insufficient number of disks for diskgroup "DGROUP3"
ORA-15063: ASM discovered an insufficient number of disks for diskgroup "DGROUP2"
ORA-15063: ASM discovered an insufficient number of disks for diskgroup "DGROUP1"
In trying to determine the cause of the problem, you issue this query:

SQL> show parameter asm -

What is the cause of the error?

As DBA for the Rebalance, you have decided that you need to facilitate some redundancy in your database. Using ASM, you want to create a disk group that will provide for the greatest amount of redundancy for your ASM data (you do not have advanced SAN mirroring technology available to you, unfortunately).
Which of the following commands would create a disk group that would offer the maximum in data redundancy?

How can you reverse the effects of an ALTER DISKGROUP ... DROP DISK command if it has NOT yet completed?

To reference existing ASM files, you need to use a fully qualified ASM filename. Your development database has a disk group named DG2A, the database name is DEV19, and the ASM file that you want to reference is a datafile for the USERS02 tablespace.
Which of the following is a valid ASM filename for this ASM file?

Which background process coordinates the rebalance activity for disk groups?

On the development database rac0, there are six raw devices: /dev/raw/raw1 through /dev/raw/raw6. /dev/raw/raw1 and /dev/raw/raw2 are 8GB each, and the rest are 6GB each.
An existing disk group +DATA1, of NORMAL REDUNDANCY, uses /dev/raw/raw1 and /dev/raw/raw2.
Which series of the following commands will drop one of the failure groups for +DATA1, create a new disk group +DATA2 using two of the remaining four raw devices, and then cancel the drop operation from +DATA1?

Which type of database file is spread across all disks in a disk group?

How can you reverse the effects of an ALTER DISKGROUP ... DROP DISK command if it has already completed?