Scribd
Upload
3 views

knowledge_base_restore_point

Uploaded by

kapil Jadhav
Copyright
© © All Rights Reserved
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
3 views

knowledge_base_restore_point

Uploaded by

kapil Jadhav
Copyright
© © All Rights Reserved
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 3

SQL> show parameter reco

NAME TYPE VALUE


------------------------------------ ----------- ------------------------------
control_file_record_keep_time integer 7
db_recovery_file_dest string +RECO_PRU
db_recovery_file_dest_size big integer 500G
db_unrecoverable_scn_tracking boolean TRUE
recovery_parallelism integer 0
remote_recovery_file_dest string
SQL>
SQL>
SQL> select flashback_on from gv$database;

FLASHBACK_ON
------------------
NO
NO

SQL> set lines 200 pages 1000


SELECT NAME,
ROUND((TOTAL_MB)/1024,2) TOTAL_GB,
ROUND((FREE_MB)/1024,2) FREE_GB,
ROUND((TOTAL_MB-FREE_MB)/1024,2) USED_GB
FROM V$ASM_DISKGROUP;
SQL> 2 3 4 5
NAME TOTAL_GB FREE_GB USED_GB
------------------------------ ---------- ---------- ----------
RECO_PRF 0 0 0
DBFS_PRF 0 0 0
DATA_DR 0 0 0
DBFS_DR 0 0 0
RECO_DR 0 0 0
DATA_PRF 0 0 0
DATA_PRU 29790 3279.25 26510.75
DBFS_PRU 1512.25 1510.82 1.43
RECO_PRU 2052 1924.34 127.66

9 rows selected.

SQL>
SQL>
SQL>
SQL>
SQL>
SQL> archive log list
Database log mode Archive Mode
Automatic archival Enabled
Archive destination +RECO_PRU
Oldest online log sequence 80
Next log sequence to archive 85
Current log sequence 85
SQL>
SQL>
SQL> show parameter reco

NAME TYPE VALUE


------------------------------------ ----------- ------------------------------
control_file_record_keep_time integer 7
db_recovery_file_dest string +RECO_PRU
db_recovery_file_dest_size big integer 500G
db_unrecoverable_scn_tracking boolean TRUE
recovery_parallelism integer 0
remote_recovery_file_dest string
SQL>
SQL>
SQL> alter system set db_recovery_file_dest_size=1T;

System altered.

SQL> show parameter reco

NAME TYPE VALUE


------------------------------------ ----------- ------------------------------
control_file_record_keep_time integer 7
db_recovery_file_dest string +RECO_PRU
db_recovery_file_dest_size big integer 1T
db_unrecoverable_scn_tracking boolean TRUE
recovery_parallelism integer 0
remote_recovery_file_dest string
SQL>
SQL>
SQL> archive log list
Database log mode Archive Mode
Automatic archival Enabled
Archive destination +RECO_PRU
Oldest online log sequence 80
Next log sequence to archive 85
Current log sequence 85
SQL>
SQL>
SQL>
SQL> show parameter reco

NAME TYPE VALUE


------------------------------------ ----------- ------------------------------
control_file_record_keep_time integer 7
db_recovery_file_dest string +RECO_PRU
db_recovery_file_dest_size big integer 1T
db_unrecoverable_scn_tracking boolean TRUE
recovery_parallelism integer 0
remote_recovery_file_dest string
SQL>
SQL>
SQL>
SQL>
SQL>
SQL>
SQL> show parameter reco

NAME TYPE VALUE


------------------------------------ ----------- ------------------------------
control_file_record_keep_time integer 7
db_recovery_file_dest string +RECO_PRU
db_recovery_file_dest_size big integer 1T
db_unrecoverable_scn_tracking boolean TRUE
recovery_parallelism integer 0
remote_recovery_file_dest string
SQL>
SQL>
SQL> create restore point CLEAN_DB guarantee flashback database;

Restore point created.

SQL> select * from gv$restore_point;

INST_ID SCN DATABASE_INCARNATION# GUA STORAGE_SIZE TIME


---------- ---------- --------------------- --- ------------
---------------------------------------------------------------------------
RESTORE_POINT_TIME PRE
--------------------------------------------------------------------------- ---
NAME
PDB CLE PDB_INCARNATION# CON_ID
-----------------------------------------------------------------------------------
--------------------------------------------- --- --- ---------------- ----------
1 9.3841E+12 2 YES 1468006400 26-AUG-19
12.53.32.000000000 PM
YES
CLEAN_DB
NO NO 0 0

2 9.3841E+12 2 YES 1468006400 26-AUG-19


12.53.32.000000000 PM
YES
CLEAN_DB
NO NO 0 0

SQL> select sysdate from dual;

SYSDATE
-------------------
26-08-2019 12:54:00

SQL> select flashback_on from gv$database;

FLASHBACK_ON
------------------
RESTORE POINT ONLY
RESTORE POINT ONLY

SQL>

In one of the oracle note (Flash Recovery area - Space management Warning & Alerts
(Doc ID 305812.1)), it is mentioned that if flashback log space got exhausted for
any reason, it won't cause any issue and database start over-writing old flash
back logs.
For example, We want to know what will happen in below scenario:
db_recovery_file_dest_size is set 20G.
db_flashback_retention_target is set for 1 hours.
Due to excessive activity on database, lot of flashback logs been generated and has
crossed the threshold (20G) within half hour.
Please clear us what will happen next? whether database will be hung? Or it will
start overwriting of flashback logs?

You might also like