[Free] 2018(Jan) EnsurePass Testinsides Oracle 1z0-053 Dumps with VCE and PDF 391-400
Oracle Database 11g: Administration II
Question No: 391 – (Topic 11)
You executed the following query:
SELECT oldest_flashback_scn, oldest_flashback_time FROM V$FLASHBACK_DATABASE_LOG;
Considering that all the redo logs are available, what information can you derive from the output of the preceding query?
The time when the last flashback operation in your database was performed
The time when the first flashback operation in your database was performed
The approximate time and the lowest system change number (SCN) to which you can flash back your database
The system change number (SCN) and the time when the Flashback Database was enabled in the database instance
Answer: C Explanation:
V$FLASHBACK_DATABASE_LOG displays information about the flashback data. Use this view to help estimate the amount of flashback space required for the current workload.
Question No: 392 – (Topic 11)
The EMP table has some discrepancy in data entry with a particular employee ID. You execute the query as shown in the Exhibit to retrieve all versions of the row that exist between two SCNs.View the Exhibit.
Which two statements about the results of the query shown in the Exhibit are correct? (Choose two.)
The LAST_SCN value in the first row is NULL, which means that the versions of the row still exist at SCN 6636300.
The LAST_SCN value in the second row in NULL, which means that the version of the row still exists at SCN 6636300.
The LAST_SCN value in the third row is 6636280, which means that the version of row exists above SCN 6636280.
The LAST_SCN value in the second row is NULL, which means that the version of the row no longer exists because it was deleted.
Answer: A,D Explanation:
Using Oracle Flashback Transaction Query with Oracle Flashback Version Query (link) The query uses Oracle Flashback Version Query pseudocolumns:
SELECT versions_xid XID, versions_startscn START_SCN, versions_endscn END_SCN, versions_operation OPERATION, empname, salary
VERSIONS BETWEEN SCN MINVALUE AND MAXVALUE
WHERE empno = 111; Results are similar to:
C:\Users\albo\Desktop\1-1.jpg 3 rows selected.
The results table rows are in descending chronological order.
->The third row corresponds to the version of the row in the table emp that was inserted in the table when the table was created.
->The second row corresponds to the row in emp that the erroneous transaction
->The first row corresponds to the version of the row in emp that was reinserted with a new employee name.
Question No: 393 – (Topic 11)
Examine the output of the query that you executed to list the objects in the recycle bin:
You verified that no table named SALES_TAB exists in the schema. Then you executed the following command to purge the objects in the recycle bin:
SQLgt; PURGE TABLE sales_tab;
What would be the outcome of this command?
All three tables in the recycle bin are purged
Only the table with the oldest DROPSCN is purged
The command returns an error because multiple entries with the same name exist in the recycle bin
Only the table with the latest DROPSCN is purged
Question No: 394 – (Topic 11)
User SCOTT wants to back out the transactions on the REGIONS table in his schema. As a DBA, which commands must you execute to enable SCOTT to flash back the transactions? (Choose four.)
ALTER DATABASE FLASHBACK ON;
GRANT SELECT ANY TRANSACTION TO scott;
GRANT EXECUTE ON dbms_flashback TO scott;
ALTER DATABASE ADD SUPPLEMENTAL LOG DATA;
ALTER TABLESPACE undots1 RETENTION GUARANTEE;
ALTER DATABASE ADD SUPPLEMENTAL LOG DATA (PRIMARY KEY) COLUMNS;
Topic 12, Additional Flashback Operations
Question No: 395 – (Topic 12)
You need to maintain a record of all transactions on some tables for at least three years. Automatic undo management is enabled for the database.
What must you do accomplish this task?
Enable supplemental logging for the database.
Specify undo retention guarantee for the database
Create Flashback Data Archive in the tablespace where the tables are stored.
Create Flashback Data Archive and enable Flashback Data Archive for specific tables
Question No: 396 – (Topic 12)
Which of the following statements is true regarding implementing a Flashback Table recovery?
An SCN is never used to perform a Flashback Table recovery.
If a significant number of changes have been made to the table, row movement must be enabled.
The tablespace must be offline before performing a Flashback Table recovery.
Flashback Table recovery is completely dependent on the availability of undo data in the undo tablespace.
Question No: 397 – (Topic 12)
You enabled Flashback Data Archive on the INVENTORY table. Which DDL operation is supported on the table after enabling Flashback Data Archive?
Drop the table.
Partition the table
Truncate the table.
Add a column to the table.
Rename a column in the table.
Answer: D Explanation:
Flashback Data Archive supports only these DDL statements:
->ALTER TABLE statement that does any of the following: Adds, drops, renames, or modifies a column
Adds, drops, or renames a constraint
Drops or truncates a partition or subpartition operation
->TRUNCATE TABLE statement
->RENAME statement that renames a table
Flashback Data Archive does not support DDL statements that
->move, split, merge, or coalesce partitions or subpartitions,
->or convert LONG columns to LOB columns.
Question No: 398 – (Topic 12)
Flashback Database relies on which technologies to recover to a point in time?
Flashback Data Archive
Flashback logs in the flash recovery area
RMAN command line
None of the above
Question No: 399 – (Topic 12)
Which are the two prerequisites before setting up Flashback Data Archive? (Choose two.)
Flash recovery area must be defined
Undo retention guarantee must be enabled.
Database must be running in archivelog mode.
Automatic undo management must be enabled.
The tablespace in which the Flashback Data Archive is created must have automatic segment space Management (ASSM).
Question No: 400 – (Topic 12)
You want to track and store all transactional changes to a table over its lifetime.
To accomplish this task, you enabled Flashback Data Archive with the retention of 5 years.
After some time, the business requirement changed and you were asked to change the retention from 5 years to 3 years.
To accomplish this, you issued the following command:
ALTER FLASHBACK ARCHIVE fla1 MODIFY RETENTION 3 YEAR;
What is the implication of this command?
The command produces an error because the retention time cannot be reduced.
All historical data is retained but the subsequent flashback data archives are maintained for only three years.
All historical data is purged and the new flashback data archives are maintained for three years.
All historical data older than three years is purged from the flashback archive FLA1.
|Lowest Price Guarantee||Yes||No||No|
|Free VCE Simulator||Yes||No||No|