Free Download 1z0-066 Examp Dump: Oracle.1z0-066.PracticeTest.2018-04-09.55q.tqb

File Info

Exam	Oracle Database 12c: Data Guard Administration
Number	1z0-066
File Name	Oracle.1z0-066.PracticeTest.2018-04-09.55q.tqb
Size	752 KB
Posted	Apr 09, 2018
Download	Oracle.1z0-066.PracticeTest.2018-04-09.55q.tqb

How to open VCEX & EXAM Files?

Files with VCEX & EXAM extensions can be opened by ProfExam Simulator.

Download
ProfExam Simulator

Purchase

Coupon: MASTEREXAM
With discount: 20%

Demo Questions

Question 1

A data file on one of your physical standby databases has been accidentally deleted and you must restore and recover it.

All the archive logs required for recovery are still on disk in the directory pointed to by the log_archive_dest_1 parameter.

Which three steps must be performed to restore the missing file and recover the standby database while it is in the MOUNT state?

Recover the datafile by using the RMAN RECOVER DATAFILE command
Restart the redo apply.
Restore the datafile by using the RMAN RESTORE DATAFILE command.
Stop the redo apply.
Recover the database by using the RMAN RECOVER DATABASE command.

Correct answer: CDE

Explanation:

Recovery from Loss of Datafiles on the Standby Database Connect SQL*Plus to the standby database. Stop Redo Apply using the SQL ALTER DATABASE ... statement. In a separate terminal, start RMAN and connect to both the standby and recovery catalog databases (use the TARGET keyword to connect to the standby instance). Issue the following RMAN commands to restore and recover datafiles on the standby database:RESTORE DATAFILE <n,m,...>; RECOVER DATABASE; To restore a tablespace, use the RMAN 'RESTORE TABLESPACE tbs_name1, tbs_name2, ...' command. At the SQL*Plus prompt, restart Redo Apply using the SQL ALTER DATABASE ... statement. References: https://docs.oracle.com/cd/E11882_01/server.112/e41134/rman.htm

Recovery from Loss of Datafiles on the Standby Database

Connect SQL*Plus to the standby database.
Stop Redo Apply using the SQL ALTER DATABASE ... statement.
In a separate terminal, start RMAN and connect to both the standby and recovery catalog databases (use the TARGET keyword to connect to the standby instance).
Issue the following RMAN commands to restore and recover datafiles on the standby database:
RESTORE DATAFILE <n,m,...>;
RECOVER DATABASE;
To restore a tablespace, use the RMAN 'RESTORE TABLESPACE tbs_name1, tbs_name2, ...' command.
At the SQL*Plus prompt, restart Redo Apply using the SQL ALTER DATABASE ... statement.

References: https://docs.oracle.com/cd/E11882_01/server.112/e41134/rman.htm

Question 2

You administer a Data Guard environment consisting of a primary and three physical standby databases.

One physical standby database is used for disaster recovery, one is used for reporting, and one is used as a replica for testing.

The standby database used for testing is occasionally converted into a snapshot standby database and then converted back to a physical standby.

The physical standby database is the only standby that is a mandatory destination.

The broker configuration operates in MAXIMUM PERFORMANCE mode.

Which ARCHIVELOG DELETION POLICY should be set, so that archive logs generated on the primary database are not deleted before they are consumed appropriately on each of the standby databases, but which allows them to be deleted form the primary as soon as it is safe to do so?

CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;
CONFIGURE ACHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
CONFIGURE ACHIVELOG DELETION POLICY TO SHIPPED TO ALL STANDBY;
CONFIGURE ACHIVELOG DELETION POLICY TO SHIPPED TO STANDBY;
CONFIGURE ACHIVELOG DELETION POLICY TO NONE;

Correct answer: B

Explanation:

You can change this default deletion policy using the following RMAN command:CONFIGURE ARCHIVELOG DELETION POLICY TO [CLEAR | NONE | APPLIED ON STANDBY]; Use the APPLIED ON STANDBY clause so that archived redo log files that have been applied on all mandatory standby destinations will be deleted. Incorrect Answers:A: APPLIED ON ALL STANDBY is not valid.C, D: SHIPPED TO is not valid.E: Use the NONE clause so that archived redo logs in flash recovery area that were backed up or obsolete as per the RMAN retention policy are eligible for deletion. This is the default configuration. Archived redo log files that are backed up or obsolete are deleted to make space if the disk space in the flash recovery area becomes full.References: https://docs.oracle.com/cd/B19306_01/server.102/b14239/rman.htm#i1031870

You can change this default deletion policy using the following RMAN command:

CONFIGURE ARCHIVELOG DELETION POLICY TO [CLEAR | NONE | APPLIED ON STANDBY];

Use the APPLIED ON STANDBY clause so that archived redo log files that have been applied on all mandatory standby destinations will be deleted.

Incorrect Answers:

A: APPLIED ON ALL STANDBY is not valid.

C, D: SHIPPED TO is not valid.

E: Use the NONE clause so that archived redo logs in flash recovery area that were backed up or obsolete as per the RMAN retention policy are eligible for deletion. This is the default configuration. Archived redo log files that are backed up or obsolete are deleted to make space if the disk space in the flash recovery area becomes full.

References: https://docs.oracle.com/cd/B19306_01/server.102/b14239/rman.htm#i1031870

Question 3

Which four factors can influence the rate of SQL apply on a logical standby database?

the size of the undo tablespace on the logical standby database
the number of full table scans performed by SQL apply
the number of coordinator processes on the standby database instance
the size of the shared pool
the number of APPLIER processes
the number of PREPARER processes

Correct answer: BDEF

Explanation:

B: If a table still does not have any unique index specified on the logical standby database, this may cause UPDATE statements to do full table scans on the logical standby database. You can remedy that by adding a unique index on the a column on the logical standby database.E: SQL Apply uses a collection of background processes to apply changes from the primary database to the logical standby database.During apply processing:The ANALYZER process identifies dependencies between different transactions. The COORDINATOR process (LSP) assigns transactions to different appliers and coordinates among them to ensure that dependencies between transactions are honored. The APPLIER processes applies transactions to the logical standby database under the supervision of the coordinator process. F: The PREPARER process is used during the log mining process, which is part of the SQL apply process.D: The Shared Pool is used by the preparar and Builder proccesses.Figure: SQL Apply Processing Incorrect Answers:C: There is only one coordinator process.References: https://docs.oracle.com/cd/B28359_01/server.111/b28294/manage_ls.htm

E: SQL Apply uses a collection of background processes to apply changes from the primary database to the logical standby database.

During apply processing:

The ANALYZER process identifies dependencies between different transactions.
The COORDINATOR process (LSP) assigns transactions to different appliers and coordinates among them to ensure that dependencies between transactions are honored.
The APPLIER processes applies transactions to the logical standby database under the supervision of the coordinator process.

F: The PREPARER process is used during the log mining process, which is part of the SQL apply process.

D: The Shared Pool is used by the preparar and Builder proccesses.

Figure: SQL Apply Processing