You want to create a guaranteed restore point for your database by executing the
command: SQL> CREATE RESTORE POINT dbrsp1 GUARANTEE FLASHBACK
DATABASE; Identify two prerequisites for the successful execution of this command.
A.
The recyclebin must be enabled for the database.
B.
Undo retention guarantee must be enabled.
C.
A database backup must be taken.
D.
The database must be running in archivelog mode.
E.
Fast Recovery Area must be enabled.
F.
Flashback Database must be enabled.
DF
and E too , You must have a fast recovery area enabled, because flashback logs can only be stored in the fast recovery area
AE.
F is wrong :
SYS@orcl 18-JAN-16>ALTER DATABASE FLASHBACK OFF;
Database altered.
SYS@orcl 18-JAN-16>CREATE RESTORE POINT dbrsp1 GUARANTEE FLASHBACK
DATABASE; 2
Restore point created.
SYS@orcl 18-JAN-16>
https://docs.oracle.com/database/121/BRADV/flashdb.htm#BRADV586
Prerequisites for Flashback Database and Guaranteed Restore Points
To ensure successful operation of Flashback Database and guaranteed restore points, you must first set some key database options.
Flashback Database
Configure the following database settings before enabling Flashback Database:
Your database must be running in ARCHIVELOG mode, because archived logs are used in the Flashback Database operation.
You must have a fast recovery area enabled, because flashback logs can only be stored in the fast recovery area.
…
Guaranteed Restore Points
To use guaranteed restore points, the database must satisfy the following ***additional*** prerequisite: the COMPATIBLE initialization parameter must be set to 10.2.0 or greater
I think F should be correct, it does not have any sense. Can you generated flasback log files if flashback is not enable?
SYS@orcl 18-JAN-16>ALTER DATABASE FLASHBACK OFF;
Database altered.
SYS@orcl 18-JAN-16>CREATE RESTORE POINT dbrsp1 GUARANTEE FLASHBACK DATABASE;
Restore point created.
SYS@orcl 18-JAN-16>create table t(id integer);
Table created.
SYS@orcl 18-JAN-16>drop table t;
Table dropped.
SYS@orcl 18-JAN-16>select flashback_on from v$database;
FLASHBACK_ON
——————
RESTORE POINT ONLY
SYS@orcl 18-JAN-16>SELECT
log# as “Log No”,
thread# as “Thread No”,
sequence# as “Seq No”,
name,
bytes/1024/1024/1024 as “Size(GB)”,
first_change# as “First Chg No”,
first_time
FROM
v$flashback_database_logfile;
Log No Thread No Seq No
———- ———- ———-
NAME
——————————-
Size(GB) First Chg No FIRST_TIM
———- ———— ———
1 1 1
/u01/app/oracle/fast_recovery_area/ORCL/flashback/o1_mf_c9rkxls3_.flb
.048828125 17941968 18-JAN-16
2 1 2
/u01/app/oracle/fast_recovery_area/ORCL/flashback/o1_mf_c9rkxmw6_.flb
.048828125 17946903 18-JAN-16
3 1 1
/u01/app/oracle/fast_recovery_area/ORCL/flashback/o1_mf_c9rmkvvg_.flb
.048828125 0
SYS@orcl 18-JAN-16>drop restore point dbrsp1;
Restore point dropped.
SYS@orcl 18-JAN-16>select flashback_on from v$database;
FLASHBACK_ON
——————
NO
SYS@orcl 18-JAN-16>SELECT
log# as “Log No”,
thread# as “Thread No”,
sequence# as “Seq No”,
name,
bytes/1024/1024/1024 as “Size(GB)”,
first_change# as “First Chg No”,
first_time
FROM
v$flashback_database_logfile ;
no rows selected
SYS@orcl 18-JAN-16>
Yes, I tested too and you are right. What is the point then in putting flashback on
DE