You enabled the flashback logging feature， but you have not specified the location of the flash recovery area. Which location would be used as the default location for the flash recovery area？（）

A .  The database must be in ARCHIVELOG mode B .  The database must be in MOUNT EXCLUSIVE mode C .  The database must be opened in RESTRICTED mode D .  The database instance must be started in the NOMOUNT state E .  The database instance must have the keep buffer pool defined

A . Because row IDs may change during the flashback operation B . Because the object number changes after the flashback operation C . Because the rows are retrieved from the recycle bin during the flashback operation D . Because the table is moved forward and back to a temporary during the flashback opertio

A .  when a table is dropped and you restore it from the Recycle Bin B .  when a user’s schema is dropped and you recover the user’s schema C .  when some incorrect data is inserted in the table and you retrieve the table to a state that was at a certain timestamp D .  when a row of a table is updated frequently and committed， and you view all the versions of the row within a specific duratio

A . Database must be running in archivelog mode. B . Automatic undo management must be enabled. C . Undo retention guarantee must be enabled. D . The tablespace on which the Flashback Data Archive is created must be managed with Automatic Segment Space Management (ASSM).

A .  Flashback logs are not archived. B .  Flashback logs are maintained in redo log files. C .  Flashback logs are maintained in the Flash Recovery Area. D .  Flashback logs are used to maintain Flashback Database related errors. E .  Flashback logs need to be cleared manually after you disable Flashback Database.

A .   STARTUP MOUNT EXCLUSIVE  ALTER DATABASE FLASHBACK ON；  ALTER DATABASE OPEN； B .   STARTUP MOUNT  ALTER DATABASE FLASHBACK ON；  ALTER DATABASE OPEN RESETLOGS； C .   STARTUP MOUNT EXCLUSIVE  ATLER DATABASE ARCHIVELOG；  ALTER DATABASE FLASHBACK ON；  ALTER DATABASE OPEN RESETLOGS； D .   STARTUP MOUNT  ALTER DATABASE ARCHIVELOG；  ALTER DATABASE FLASHBACK ON；  ALTER DATABASE OPEN；

A .  to undo the changes made to the EMP table since the specified time B .  to restore the EMP table that was wrongly dropped from the database C .  to view the transactions that have modified the EMP table since the specified time D .  to view the changes made to the EMP table for one or more rows since the specified time

A . The database must be in ARCHIVELOG mode B . The database must be in MOUNT EXCLUSIVE mode C . The database must be opened in RESTRICTED mode D . The database instance must be started in the NOMOUNT state E . The database instance must have the keep buffer pool defined

A . to undo the changes made to the EMP table since the specified time B . to restore the EMP table that was wrongly dropped from the database C . to view the transactions that have modified the EMP table since the specified time D . to view the changes made to the EMP table for one or more rows since the specified time E . to recover the EMP table to a point in time in the past by restoring the most recent backu

A . The Flashback Archive FLA1 is dropped only if it is empty. B . The tablespace having Flashback Archive is dropped. C . The Flashback Archive FLA1 is dropped after moving the existing data in it to the default Flashback Archive. D . The Flashback Data Archive and historical data are dropped.

A . The FLASHBACK TABLE statement will not be written to the alert log file. B . The changes made to the EMP table since the specified time will be undone. C . The EMP table that was dropped by mistake from the database will be restored. D . The FLASHBACK TABLE statement will be executed within a single transaction. E . The FLASHBACK TABLE statement will not maintain the existing indexes on the EMP table.  F . The list of transactions that have modified the EMP table since the specified time will be displayed.

A .  V$DATABASE B .  V$FLASHBACK_DATABASE_STAT C .  V$FLASHBACK_DATABASE_LOG D .  V$RECOVERY_FILE_DEST

A .  The database must be started in the MOUNT EXCLUSIVE state. B .  The database must have multiplexed control files. C .  The database must be opened by using a text-based parameter file instead of a server parameter file （SPFILE）. D .  The database must be in ARCHIVELOG mode. E .  The database must be in the NOMOUNT state. F .  The database must be opened in RESTRICTED mode.

A .  The database does not record flashback logs for MY_TABLESPACE B .  The tables residing in MY_TABLESPACE are not protected by the Recycle Bin. C .  All the tablespaces except MY_TABLESPACE can be recovered using Flashback Database feature. D .  None of the flashback technologies， such as Flashback Table， Flashback Transaction Query and Flashback Version Query can be used to recover individual rows within the objects from MY_TABLESPACE

A . the time when the last flashback operation in your database was performed B . the time when the first flashback operation in your database was performed C . a list of flashback operations performed in your database using SCN and time D . the approximate time and the lowest system change number （SCN） to which you can flash back your database

A . the location used for control files B . the location used for redo log files C . the location set by using $ORACLE_BASE D . the location set by using $ORACLE_HOME E . the location set by using CORE_DUMP_DEST F . the location set by using BACKGROUND_DUMP_DEST

A .  Drop the table. B .  Partition the table. C .  Truncate the table. D .  Add a column to the table. E .  Rename a column in the table.

A .  when you want to restore an important table that is dropped from the Recycle Bin B .  when you want to obtain the SQL statements to undo the deletion of some important records from a table by a transaction C . when you want to restore a dropped user’s schema D .  when a row of a table is updated many times within a specific time period and you want all the versions of the row in the specified time period

A . to undo the changes made to the EMP table since the specified time B . to restore the EMP table that was wrongly dropped from the database C . to view the transactions that have modified the EMP table since the specified time D . to view the changes made to the EMP table for one or more rows since the specified time E . to recover the EMP table to a point in time in the past by restoring the most recent backu

A .  when you want to restore a table that has been dropped from the Recycle Bin B .  when you want to identify the transaction ID of the transaction that deleted some important records from a table C .  when you want to recover the schema of a dropped user D . when you want to restore a dropped tablespace

A .  Flashback logs are not deleted. B .  Flashback logs are deleted automatically. C .  Flashback logs are deleted only if you are using Recovery Manager （RMAN） D .  Flashback logs are deleted only if you are using Oracle Manager Files （OFM） E .  Flashback logs are deleted only if you are using Automatic Storage Management （ASM）

A .  Database must be running in archivelog mode. B .  Automatic undo management must be enabled. C .  Undo retention guarantee must be enabled. D .  The tablespace on which the Flashback Data Archive is created must be managed with Automatic Segment Space Management （ASSM）.

A .  Because row IDs may change during the flashback operation B .  Because the object number changes after the flashback operation C .  Because the rows are retrieved from the recycle bin during the flashback operation D .  Because the table is moved forward and back to a temporary during the flashback opertio

A. Because row IDs may change during the flashback operation B. Because the object number changes after the flashback operation C. Because the rows are retrieved from the recycle bin during the flashback operation D. Because the table is moved forward and back to a temporary during the flashback operation