31.
You want to migrate your database to ASM, so you've done a clean shutdown, made a
closed backup of the entire database, noted the location of your control files and online
redo log files, and changed your spfile to use OMF. The last step is to run an RMAN script
to do the conversion. Using the following steps, what is the correct order in which the following
RMAN commands should be executed?
1. STARTUP NOMOUNT
2. ALTER DATABASE OPEN RESETLOGS
3. SQL "ALTER DATABASE RENAME 'logfile1 path' TO '+dgrp4 '" # plus all other logfiles
4. SWITCH DATABASE TO COPY
5. BACKUP AS COPY DATABASE FORMAT '+dgrp4'
6. ALTER DATABASE MOUNT
7. RESTORE CONTROLFILE FROM 'controlfile_location'
2. ALTER DATABASE OPEN RESETLOGS
3. SQL "ALTER DATABASE RENAME 'logfile1 path' TO '+dgrp4 '" # plus all other logfiles
4. SWITCH DATABASE TO COPY
5. BACKUP AS COPY DATABASE FORMAT '+dgrp4'
6. ALTER DATABASE MOUNT
7. RESTORE CONTROLFILE FROM 'controlfile_location'
- A.2, 5, 3, 1, 7, 6, 4
- B.1, 7, 6, 5, 4, 3, 2
- C.5, 1, 2, 7, 4, 6, 3
- D.7, 3, 1, 5, 6, 2, 4
- Answer & Explanation
- Report
Answer : [B]
Explanation :
Explanation :
| After the RMAN script is run and the database is up and running successfully, you may delete the old database files. |
32.
As DBA for the Rebel Alliance 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?
- A.
CREATE DISKGROUP dg_alliance1 NORMAL REDUNDANCY failgroup diskcontrol1 DISK 'c:\oracle\asm_disk\_file_disk3' NAME file_diska1 failgroup diskcontrol2 DISK 'c:\oracle\asm_disk\_file_disk4' NAME file_diskb1
- B.
CREATE DISKGROUP dg_alliance1 EXTERNAL REDUNDANCY failgroup diskcontrol1 DISK 'c:\oracle\asm_disk\_file_disk3' NAME file_diska1;
- C.
CREATE DISKGROUP dg_alliance1 HIGH REDUNDANCY failgroup diskcontrol1 DISK 'c:\oracle\asm_disk\_file_disk1' NAME file_ disk1 failgroup diskcontrol2 DISK 'c:\oracle\asm_disk\_file_disk2' NAME file_ disk2 failgroup diskcontrol2 DISK 'c:\oracle\asm_disk\_file_disk3' NAME file_ disk3;
- D.
CREATE DISKGROUP dg_alliance1 MAXIMUM REDUNDANCY failgroup diskcontrol1 DISK 'c:\oracle\asm_disk\_file_disk1' NAME file_ disk1 failgroup diskcontrol2 DISK 'c:\oracle\asm_disk\_file_disk2' NAME file_ disk2 failgroup diskcontrol2 DISK 'c:\oracle\asm_disk\_file_disk3' NAME file_ disk3 failgroup diskcontrol2 DISK 'c:\oracle\asm_disk\_file_disk4' NAME file_ disk4;
- E.None of the above
- Answer & Explanation
- Report
Answer : [C]
Explanation :
Explanation :
| High redundancy is the highest redundancy setting available in ASM, or to the Alliance in this case. This will result in a double-mirrored ASM disk group. |
33.
When starting up your ASM instance, you receive the following error:
SQL> startup pfile=?/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 alterations performed
ORA-15063: ASM discovered an insufficient number of disks for disk group
"DGROUP3"
ORA-15063: ASM discovered an insufficient number of disks for disk group
"DGROUP2"
ORA-15063: ASM discovered an insufficient number of disks for disk group
"DGROUP1"
In trying to determine the cause of the problem, you issue this query:
SQL> show parameter asm
NAME TYPE VALUE
------------------------------------ ----------- -------------------------_
asm_allow_only_raw_disks boolean FALSE
asm_diskgroups string DGROUP1, DGROUP2, DGROUP3
asm_diskstring string
asm_power_limit integer 1
asm_preferred_read_failure_groups string
What is the cause of the error?
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 alterations performed
ORA-15063: ASM discovered an insufficient number of disks for disk group
"DGROUP3"
ORA-15063: ASM discovered an insufficient number of disks for disk group
"DGROUP2"
ORA-15063: ASM discovered an insufficient number of disks for disk group
"DGROUP1"
In trying to determine the cause of the problem, you issue this query:
SQL> show parameter asm
NAME TYPE VALUE
------------------------------------ ----------- -------------------------_
asm_allow_only_raw_disks boolean FALSE
asm_diskgroups string DGROUP1, DGROUP2, DGROUP3
asm_diskstring string
asm_power_limit integer 1
asm_preferred_read_failure_groups string
What is the cause of the error?
- A.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.
- B.The format of the ASM_DISKGROUPS parameter is incorrect. It should reference the disk group numbers, not the names of the disk groups.
- C.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.
- D.The ASM_DISKSTRING parameter is not set; therefore disk discovery is not possible.
- E.There is insufficient information to solve this problem.
- Answer & Explanation
- Report
Answer : [D]
Explanation :
Explanation :
| The ASM_DISKSTRING parameter is not set correctly. When the ASM instance is started, it will use the ASM_DISKSTRING to do ASM disk discovery. Correct the ASM_DISKSTRING parameter, and restart the instance to correct the problem. |
34.
When an ASM instance receives a SHUTDOWN NORMAL command, what command does it pass
on to all database instances that rely on the ASM instance's disk groups?
- A.TRANSACTIONAL
- B.IMMEDIATE
- C.ABORT
- D.NORMAL
- E.None of the above
- Answer & Explanation
- Report
Answer : [E]
Explanation :
Explanation :
| 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. |
35.
Which initialization parameter in an ASM instance specifies the disk groups to be automatically
mounted at instance startup?
- A.ASM_DISKMOUNT
- B.ASM_DISKGROUP
- C.ASM_DISKSTRING
- D.ASM_MOUNTGROUP
- Answer & Explanation
- Report
Answer : [B]
Explanation :
Explanation :
| The initialization parameter ASM_DISKGROUP, valid only in an ASM instance, specifies the disk groups to be automatically mounted when the ASM instance starts. ASM_DISKSTRING is operating system–dependent and restricts the file-system devices that can be used to create disk groups. ASM_DISKMOUNT and ASM_MOUNTGROUP are not valid initialization parameters. |
|
|
||||||||||||||||||||||||||||
