Download Oracle Database 12c: Data Guard Administration.1z0-066.BrainDumps.2018-12-19.55q.vcex

Incorrect Answers:E: NOT ALLOWED - Either this is a standby database and the primary database has not been switched first, or this is a primary database and there are no standby databases.

Recovery from Loss of Datafiles on the Standby Database 1. Connect SQL*Plus to the standby database. 2. Stop Redo Apply using the SQL ALTER DATABASE ... statement. 3. 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). 4. Issue the following RMAN commands to restore and recover datafiles on the standby database:RESTORE DATAFILE <n,m,...>; RECOVER DATABASE; 5. To restore a tablespace, use the RMAN 'RESTORE TABLESPACE tbs_name1, tbs_name2, ...' command. 6. 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

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

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 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

B: A snapshot standby database can be converted back into a physical standby database at any time.E: You create a logical standby database by first creating a physical standby database and then transitioning it to a logical standby database.Incorrect Answers:A: Oracle Database supports the installation of database software upgrades, and the application of patch sets, in a rolling fashion—with near zero database downtime—by using Data Guard SQL Apply and logical standby databases.C: A cascaded redo transport destination (also known as a terminal destination) receives primary database redo indirectly from a standby database rather than directly from a primary database. Only physical standby databases can cascade redo.D: A snapshot standby cannot be the target of a switchover or fast-start failover operation.References: https://docs.oracle.com/cd/E11882_01/server.112/e41134/create_ls.htm#SBYDB4732https://docs.oracle.com/cd/E11882_01/server.112/e41134/manage_ps.htm#SBYDB00580

There are three parameters that can be modified to control the number of processes allocated to SQL Apply: MAX_SERVERS, APPLY_SERVERS, and PREPARE_SERVERS. The following relationships must always hold true:APPLY_SERVERS + PREPARE_SERVERS = MAX_SERVERS - 3 This is because SQL Apply always allocates one process for the READER, BUILDER, and ANALYZER roles. References: https://docs.oracle.com/cd/B28359_01/server.111/b28294/manage_ls.htm

C: Flashback Database is similar to conventional point-in-time recovery in its effects. It enables you to return a database to its state at a time in the recent past. Flashback Database uses its own logging mechanism, creating flashback logs and storing them in the fast recovery area. You can only use Flashback Database if flashback logs are available. Flashback Database is used to convert a snapshot standby database back into a physical standby database.E: When we convert the physical standby database to snapshot standby database a guaranteed restore point is created. This guaranteed restore point is used to flashback a snapshot standby database to its original state.Incorrect Answers:A: Oracle Database supports the installation of database software upgrades, and the application of patch sets, in a rolling fashion—with near zero database downtime—by using Data Guard SQL Apply and logical standby databases.References:https://docs.oracle.com/cd/E11882_01/server.112/e41134/manage_ps.htm#SBYDB4803http://satya-dba.blogspot.se/2012/06/snapshot-standby-databases-oracle.html

B: the terminal standby should have a LOG_ARCHIVE_DEST_n parameter defined that points back to the primary.D: Because the standby's requests for a range of sequences involve a round-trip to the primary, be sure to specify a large enough value for the CACHE keyword when you create a sequence that will be used on an Oracle Active Data Guard standby. Otherwise, performance could suffer.E: In an Oracle Active Data Guard environment, sequences created by the primary database with the default CACHE and NOORDER options can be accessed from standby databases as well.References: https://docs.oracle.com/database/121/SBYDB/manage_ps.htm#SBYDB5164

Viewing Information About the Observer You can find information about the observer by querying the following columns in the V$DATABASE view:FS_FAILOVER_OBSERVER_HOST shows the name of the computer on which the observer is running. Here it is cats. FS_FAILOVER_OBSERVER_PRESENT shows whether or not the observer is connected to the local database. Here the value is NO. References: https://docs.oracle.com/cd/B19306_01/server.102/b14230/sofo.htm

RMAN uses a recovery catalog to track filenames for all database files in a Data Guard environment. A recovery catalog is a database schema used by RMAN to store metadata about one or more Oracle databases. The catalog also records where the online redo logs, standby redo logs, tempfiles, archived redo logs, backup sets, and image copies are created. RMAN commands use the recovery catalog metadata to behave transparently across different physical databases in the Data Guard environment. For example, you can back up a tablespace on a physical standby database and restore and recover it on the primary database. Similarly, you can back up a tablespace on a primary database and restore and recover it on a physical standby database. Incorrect Answers:A: Because a logical standby database is not a block-for-block copy of the primary database, you cannot use a logical standby database to back up the primary databaseD: Backups of standby control files and nonstandby control files are interchangeable. For example, you can restore a standby control file on a primary database and a primary control file on a physical standby database. This interchangeability means that you can offload control file backups to one database in a Data Guard environment. RMAN automatically updates the filenames for database files during restore and recovery at the databases.References:  https://docs.oracle.com/cd/E11882_01/server.112/e41134/rman.htm#SBYDB4853