RAC 11 g flashbacks and archive are separate, flash back to the area of growth, is nearly 99%, archive area space a lot! How does ability fall flashback area!
Run: select * from v $flash_recovery_area_usage t; t.
Results:
The CONTROL FILE 0.04 0 1
REDO LOG 0.4 0 4
ARCHIVED LOG 0 0 0
BACKUP PIECE 0.04 0 1
The IMAGE COPY 0 0 0
FLASHBACK LOG 98.59 45.64 2750
FOREIGN ARCHIVED LOG 0 0 0
How does ability let flashbacks area using down,,,,

CodePudding user response:

Why do you want to come down, flashback area full of automatically covering the old data, keep the latest record

CodePudding user response:

If occupy 99% database may hang up?

CodePudding user response:

Should not, 11 g flashback area full of will cover the old files before,
You can also increase flashback area space flashbacks or shorten the time,

CodePudding user response:

Database will be automatically deleted release space in theory, but does not exclude the abnormal situation lead to 100% fill lead system hangs,
But should be combined with the following consideration:
1 db_flashback_retention_target parameter value, can reduce the need to keep FLASHBACKLOG
2 increase db_recovery_file_dest_size parameter value, increase the flashback area space, (if there is enough storage space)

CodePudding user response:

Db_flashback_retention_target I set of 3 days, 4320
But there are seven days in flashback log data
Atul gawande at the select date, sum (a. YTES) as BYTES_GB from (
Select substr (to_char (t.F IRST_TIME, '- DD YYYY - MM), 1, 10) as gdate, t.B YTES as BYTES from v $flashback_database_logfile t where 1=1
) a group by atul gawande atul gawande at the date the order by the date desc;
=================
The 2020-08-29 5876023296
The 2020-08-28 14884339712
The 2020-08-27 14923988992
The 2020-08-26 13139771392
The 2020-08-25 14226161664
The 2020-08-24 14749532160
The 2020-08-23 13717356544
The 2020-08-22 9727344640

Db_recovery_file_dest_size I already set by the 110 g, total felling the recovery faster than growth,

CodePudding user response:

Look from the data, data recovery than growth slow, lead to available space more and more to less, every day now increase of 3%

CodePudding user response:

Db_flashback_retention_target set of 3 days, just say enough space, can flash back in 3 days time points, not to say that only keep 3 days,

CodePudding user response:

Is there a way to let flashback log of the space down, because my side flashback log fill, hang up a database

CodePudding user response:

What is the approximate size of file you 1 day, you rollback area size and disk size respectively is how much?

You can try to flash back to resize area a little bit small, so the rollback area space full of will automatically overwrite the previous data

CodePudding user response:

1 day of flashback log is about 18 g, the flashback zone configuration is 110 g, disk total size is 180 g,
Just a few days before configuration is 60 g, 99.99%! So expanded to 110 g, is now 88%, at present, the new data faster than automatic recovery of data,

CodePudding user response:

Write a regular deleted automatically log script

CodePudding user response:

Oracle provides no delete flashback log command! The automatic recovery!

CodePudding user response:

If is manually delete files, risk or is too high, which is a formal environment, did not dare to move

CodePudding user response:

First find out what caused the soaring space, big probability is archive, since opened the archive, then rman backup is possible or as the source of data synchronization tool library, delete the file not to delete will delete,