Oracle Database 11g: Administration II
Question No: 1 – (Topic 1)
You are managing an Oracle Database 11g ASM instance with a disk group dg01 having three disks. One of the disks in the disk group becomes unavailable because of power failure. You issued the following command to change the DISK_REPAIR_TIME attribute from 3.6 hours to 5 hours:
ALTER DISKGROUP dg01 SET ATTRIBUTE #39;disk_repair_time#39; = #39;5h#39;; To which disks in the disk group will the new value be applicable?
all disks in the disk group
all disks that are currently in OFFLINE mode
all disks that are not currently in OFFLINE mode
all disks in the disk group only if all of them are ONLINE
Answer: C Explanation:
Check out the answer options, it is tricky. The NOT OFFLINE disks equals ONLINE disks. Refer to Set the DISK_REPAIR_TIME Disk Group Attribute Appropriately.
The DISK_REPAIR_TIME disk group attribute specifies how long a disk remains offline before Oracle ASM drops the disk. If a disk is made available before the DISK_REPAIR_TIME parameter has expired, the storage administrator can issue the ONLINE DISK command and Oracle ASM resynchronizes the stale data from the mirror side. In Oracle Database 11g, the online disk operation does not restart if there is a failure of the instance on which the disk is running. You must reissue the command manually to bring the disk online.
Question No: 2 – (Topic 1)
You are managing an Oracle Database 11g ASM instance having three disks in a disk group with ASM compatibility attribute set to 11.1.0 and redundancy set to high. One of the disks in the disk group becomes unavailable because of power failure.
Which statements will be true in this scenario? (Choose all that apply.)
The disk is immediately dropped from the disk group.
The ASM tracks the extents that are modified during the outage.
The ASM migrates the extents from the unavailable disk to the remaining disks.
The disk automatically goes offline.
Question No: 3 – (Topic 1)
Which initialization parameter in an ASM instance specifies the disk groups to be automatically mounted at instance startup?
Answer: B Explanation: Refer to here
When you run the STARTUP command, this command attempts to mount the disk groups specified by the initialization parameter ASM_DISKGROUPS. If you have not entered a value for ASM_DISKGROUPS, then the ASM instance starts and Oracle displays an error that no disk groups were mounted. You can then mount disk groups with the ALTER DISKGROUP…MOUNT command.
Question No: 4 – (Topic 1)
If you use ALTER DISKGROUP … ADD DISK and specify a wildcard for the discovery string, what happens to disks that are already a part of the same or another disk group?
The command fails unless you specify the FORCE option.
The command fails unless you specify the REUSE option.
The command must be reissued with a more specific discovery string.
The other disks, already part of the disk group, are ignored.
Answer: C Explanation:
Refer to an Oracle Example for adding disk to diskgroup (link) How A Disk is Discovered
While an ASM instance is initialized, ASM discovers and examines the contents of all of the disks that are in the paths that you designated with values in the ASM_DISKSTRING initialization parameter. Disk discovery also occurs when you:
->Run the ALTER DISKGROUP…ADD DISK and ALTER DISKGROUP…RESIZE
->Query the V$ASM_DISKGROUP and V$ASM_DISK views
Disk Discovery Rules(link)
The rules for discovering ASM disks are as follows:
->ASM can discover up to 10,000 disks. That is, if more than 10,000 disks match the ASM_DISKSTRING initialization parameter, then ASM discovers only the first 10,000.
->ASM only discovers disks that contain a partition table.
ASM does not discover a disk that contains an operating system partition table, even if the disk is in an ASM disk string search path and ASM has read and write permission for the disk.
->When adding a disk, the FORCE option must be used if ASM recognizes that the disk was managed by Oracle. Such a disk appears in the V$ASM_DISK view with a status of FOREIGN. In this case, you can only add the disk to a disk group by using the FORCE keyword.
In addition, ASM identifies the following configuration errors during discovery:
->Multiple paths to the same disk
In this case, if the disk is part of a disk group, then disk group mount fails. If the disk is being added to a disk group with the ADD DISK or CREATE DISKGROUP command, then the command fails. To correct the error, adjust the ASM_DISKSTRING value so that ASM will not discover multiple paths to the same disk. Or if you are using multipathing software, then ensure that you include only the pseudo-device name in the ASM_DISKSTRING value. See quot;ASM and Multipathingquot;.
->Multiple ASM disks with the same disk header
This can be caused by having copied one disk onto another. In this case, the disk group mount operation fails.
Question No: 5 – (Topic 1)
When starting up your ASM instance, you receive the following error: SQLgt; 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: SQLgt; show parameter asm
What is the cause of the error?
The ASM_DISKGROUPS parameter is configured for three disk groups: DGROUP1, DGROUP2, and DGROUP3.
The underlying disks for these disk groups have apparently been lost.
The format of the ASM_DISKGROUPS parameter is incorrect. It should reference the disk group numbers, not the names of the disk groups
The ASM_POWER_LIMIT parameter is incorrectly set to 1. It should be set to the number of disk groups being attached to the ASM instance.
The ASM_DISKSTRING parameter is not set; therefore disk discovery is not possible.
There is insufficient information to solve this problem.
Answer: D Explanation:
ASM_DISKSTRING specifies an operating system-dependent value used by Automatic Storage Management to limit the set of disks considered for discovery. When a new disk is added to a disk group, each Automatic Storage Management instance that has the disk group mounted must be able to discover the new disk using the value of ASM_DISKSTRING.
In most cases, the default value will be sufficient. Using a more restrictive value may reduce the time required for Automatic Storage Management to perform discovery, and thus improve disk group mount time or the time for adding a disk to a disk group. A quot;?quot; at the beginning of the string gets expanded to the Oracle home directory. Depending on the operating system, wildcard characters can be used. It may be necessary to dynamically change ASM_DISKSTRING before adding a disk so that the new disk will be discovered. An attempt to dynamically modify ASM_DISKSTRING will be rejected and the old value retained if the new value cannot be used to discover a disk that is in a disk group that is already mounted.
Refer to here
Question No: 6 – (Topic 1)
You are managing an ASM instance. You previously issued the following statements:
ALTER DISKGROUP dg1 DROP DISK disk2; ALTER DISKGROUP dg1 DROP DISK disk3; ALTER DISKGROUP dg1 DROP DISK disk5;
You want to cancel the disk drops that are pending for the DG1 disk group. Which statement should you issue?
ALTER DISKGROUP dg1 UNDROP disk2, disk3, disk5;
ALTER DISKGROUP dg1 UNDROP;
ALTER DISKGROUP dg1 UNDROP DISKS;
You cannot cancel the pending disk drops.
Answer: C Explanation:
Use this clause to cancel the drop of disks from the disk group. You can cancel the pending drop of all the disks in one or more disk groups (by specifying diskgroup_name) or of all the disks in all disk groups (by specifying ALL).
This clause is not relevant for disks that have already been completely dropped from the disk group or for disk groups that have been completely dropped. This clause results in a long-running operation. You can see the status of the operation by querying the V$ASM_OPERATION dynamic performance view.
Question No: 7 – (Topic 1)
What are the recommendations for Oracle Database 11g installation to make it Optimal Flexible Architecture (OFA)-compliant? (Choose all that apply.)
ORACLE_BASE should be set explicitly.
An Oracle base should have only one Oracle home created in it.
Flash recovery area and data file location should be on separate disks.
Flash recovery area and data file location should be created under Oracle base in a non-Automatic Storage Management (ASM) setup.
Question No: 8 – (Topic 1)
You are managing an Oracle Database 11g database with ASM storage. The ASM disk
group has the COMPATIBLE.ASM attribute set to 11.1.
Which statements are true regarding extent management and allocation units in the ASM disk group? (Choose all that apply.)
The au_size disk group attribute determines the size of allocation units in the disk group.
The allocation unit size may vary but the extent size is fixed.
The allocation unit size and extent size are fixed for all the disks in a disk group and cannot be changed.
Extent management is completely automated.
Question No: 9 – (Topic 1)
The following command is executed to shut down an Automatic Storage Management (ASM) instance:
Which two statements describe the consequences of the above command? (Choose two.)
The disk groups are orderly dismounted.
The ASM instance requires recovery when it is started.
The database instance that are currently clients of the ASM instance are aborted.
The CSS daemon stops and has to be restarted before the ASM instance is restarted.
Question No: 10 – (Topic 1)
You want to perform the following operations for the DATA ASM disk group:
->Verify the consistency of the disk.
->Cross-check all the file extent maps and allocation tables for consistency.
->Check whether the alias metadata directory and file directory are linked correctly.
->Check that ASM metadata directories do not have unreachable allocated blocks.
Which command accomplishes these tasks?
ALTER DISKGROUP data CHECK;
ALTER DISKGROUP data CHECK DISK;
ALTER DISKGROUP data CHECK FILE;
ALTER DISKGROUP data CHECK DISK IN FAILURE GROUP 1;
Answer: A Explanation:
Syntax: ALTER DISKGROUP lt;disk_group_idgt; CHECK [REPAIR | NOREPAIR];
The check_diskgroup_clause lets you verify the internal consistency of Oracle ASM disk group metadata. The disk group must be mounted. Oracle ASM displays summary errors and writes the details of the detected errors in the alert log.
The CHECK keyword performs the following operations:
->Checks the consistency of the disk.
->Cross checks all the file extent maps and allocation tables for consistently.
->Checks that the alias metadata directory and file directory are linked correctly.
->Checks that the alias directory tree is linked correctly.
->Checks that Oracle ASM metadata directories do not have unreachable allocated blocks.
Refer to here
|Lowest Price Guarantee||Yes||No||No|
|Free VCE Simulator||Yes||No||No|