Oracle Database 11g: Administration II
Question No: 411 – (Topic 12)
Which of these are valid Flashback Database recovery point parameters? (Choose all that apply.)
Named recovery point
Question No: 412 – (Topic 12)
What two are the prerequisites for enabling Flashback Database? (Choose two)
The database must be in ARCHIVELOG mode
The database must be in MOUNT EXCLUSIVE mode
The database must be opened in RESTRICTED mode
The database instance must be started in the NOMOUNT state
The database instance must have the keep buffer pool defined
Question No: 413 – (Topic 12)
You execute the following FLASHBACK TABLE command:
SQLgt; FLASHBACK TABLE emp TO TIMESTAMP TO_TIMESTAMP(#39;2008-01-04 11:00:00#39;,#39;YYYY-MMDD HH24:MI:SS#39;);
Which two statements are correct? (Choose two.)
The emp table that was dropped by mistake earlier is restored.
The FLASHBACK TABLE statement is executed as a single transaction.
The FLASHBACK TABLE statement does not maintain existing indexes on the emp table.
The changes made to the emp table since the specified time are undone if no constraint is violated during flashback.
Answer: B,D Explanation: FLASHBACK TABLE (Link)
Use the FLASHBACK TABLE statement to restore an earlier state of a table in the event of human or application error. The time in the past to which the table can be flashed back is dependent on the amount of undo data in the system. Also, Oracle Database cannot restore a table to an earlier state across any DDL operations that change the structure of the table.
During an Oracle Flashback Table operation, Oracle Database acquires exclusive DML locks on all the tables specified in the Flashback list. These locks prevent any operations on the tables while they are reverting to their earlier state.
The Flashback Table operation is executed in a single transaction, regardless of the number of tables specified in the Flashback list. Either all of the tables revert to the earlier state or none of them do. If the Flashback Table operation fails on any table, then the entire statement fails.
At the completion of the Flashback Table operation, the data in table is consistent with table at the earlier time.
However, FLASHBACK TABLE TO SCN or TIMESTAMP does not preserve rowids, and FLASHBACK TABLE
TO BEFORE DROP does not recover referential constraints.
Oracle Database does not revert statistics associated with table to their earlier form. Indexes on table that exist currently are reverted and reflect the state of the table at the Flashback point. If the index exists now but did not yet exist at the Flashback point, then
the database updates the index to reflect the state of the table at the Flashback point. However, indexes that were dropped during the interval between the Flashback point and the current time are not restored.
Logical Flashback Features Useful in Backup and Recovery (Link)
The remaining flashback features operate at the logical level. The logical features documented in this chapter are as follows:
You can recover a table or set of tables to a specified point in time in the past without taking any part of the database offline. In many cases, Flashback Table eliminates the need to perform more complicated point-in-time recovery operations. Flashback Table restores tables while automatically maintaining associated attributes such as current indexes, triggers and constraints, and not requiring you to find and restore application- specific properties.
quot;Rewinding a Table with Flashback Tablequot; explains how to use this feature.
You can reverse the effects of a DROP TABLE statement.
quot;Rewinding a DROP TABLE Operation with Flashback Dropquot; explains how to use this feature.
Because the logical flashback features have uses not specific to backup and recovery, some documentation for them is located elsewhere in the documentation set.
All logical flashback features except Flashback Drop rely on undo data. Used primarily for providing read consistency for SQL queries and rolling back transactions, undo records contain the information required to reconstruct data as it existed at a past time and examine the record of changes since that past time.
Question No: 414 – (Topic 12)
What does the DB_FLASHBACK_RETENTION_TARGET parameter configure?
An upper limit on how far you can flash back the database, depending on the information in the redo logs
An upper limit on how far you can flash back the database, depending on the information in the undo tablespace
The amount of time for which the flashback data is to be kept in the flash recovery area,
provided that there is enough space
The amount of time for which the flashback data is guaranteed to be kept in the undo tablespace, provided that there is enough space
Question No: 415 – (Topic 12)
To clean up old records that are in a Flashback Data Archive and are past the retention period, what must the DBA do?
TRUNCATE the archive table.
DROP the Flashback Data Archive.
Nothing; expired rows are automatically removed.
Nothing; expired rows are moved to an archive table.
Delete entries from the archive where the metadata date retained is greater than the retention period.
Question No: 416 – (Topic 12)
A user performs an update on a table. Shortly after committing the transaction, they realize that they had an error in their WHERE clause causing the wrong rows to be updated.
Which Flashback option would allow you to undo this transaction and restore the table to its previous state?
Flashback Versions Query
Flashback Transaction Query
Answer: E Explanation: FLASHBACK TABLE
Use the FLASHBACK TABLE statement to restore an earlier state of a table in the event of human or application error. The time in the past to which the table can be flashed back is
dependent on the amount of undo data in the system. Also, Oracle Database cannot restore a table to an earlier state across any DDL operations that change the structure of the table.
Question No: 417 – (Topic 12)
View the Exhibit and examine the output.
You executed the following command to enable Flashback Data Archive on the EXCHANGE_RATE table:
ALTER TABLE exchange_rate FLASHBACK ARCHIVE; What is the outcome of this command?
The Flashback Archive is created on the same tablespace where the tables are stored.
The Flashback Archive is created on the SYSAUX tablespace.
The command generates an error because no Flashback Archive name is specified and there is no default Flashback Archive.
The table uses the default Flashback Archive.
Topic 13, Diagnosing the Database
Question No: 418 – (Topic 13)
Which setting enables the baselines by default in Oracle Database 11g?
setting the STATISTICS_LEVEL parameter to TYPICAL
adding filters to the Automatic Database Diagnostic Monitor (ADDM)
enabling Automated Maintenance Task using Oracle Enterprise Manager
setting the OPTIMIZER_USE_PENDING_STATISTICS parameter to TRUE
Question No: 419 – (Topic 13)
You plan to collect the Automatic Workload Repository (AWR) data every Monday morning for a month. You want Oracle Database to automatically create a baseline every Monday and remove the old baseline. What is the correct action to achieve this?
Create and populate a SQL Tuning Set from the AWR on every Monday.
Change the RETENTION setting for the AWR snapshots to 7 days on Monday.
Create a repeating baseline template.
Insert a finding directive for future ADDM tasks.
Question No: 420 – (Topic 13)
You need to perform a block media recovery on the tools01.dbf data file in the SALES database by using Recovery Manager (RMAN).
Which two are the prerequisites to perform this operation? (Choose two)
You must configure block change tracking file
You must have first level 1 backups for RMAN to restore blocks
You must ensure that the SALES database is mounted or open
You must have full or level 0 backups for RMAN to restore blocks
You must take the tools01.dbf data file offline before you start a block media recovery
Answer: C,D Explanation:
Prerequisites for Block Media Recovery (link)
The following prerequisites apply to the RECOVER … BLOCK command:
->The target database must run in ARCHIVELOG mode and be open or mounted with a current control file.
->If the target database is a standby database, then it must be in a consistent state,
recovery cannot be in session, and the backup must be older than the corrupted file.
->The backups of the data files containing the corrupt blocks must be full or level 0
backups and not proxy copies.
If only proxy copy backups exist, then you can restore them to a nondefault location on disk, in which case RMAN considers them data file copies and searches them for blocks during block media recovery.
->RMAN can use only archived redo logs for the recovery.
RMAN cannot use level 1 incremental backups. Block media recovery cannot survive a missing or inaccessible archived redo log, although it can sometimes survive missing redo records.
->Flashback Database must be enabled on the target database for RMAN to search
the flashback logs for good copies of corrupt blocks.
If flashback logging is enabled and contains older, uncorrupted versions of the corrupt blocks, then RMAN can use these blocks, possibly speeding up the recovery.
->The target database must be associated with a real-time query physical standby
database for RMAN to search the database for good copies of corrupt blocks.
|Lowest Price Guarantee||Yes||No||No|
|Free VCE Simulator||Yes||No||No|