A few days ago, when archiving cannot be closed due to batch data import, the archive path and the flash burst! (I am still curious about archiving. I have never met this before. I don't know why)
Ora-19815: Warning db_recovery_file_dest_size 100% used
Select * from v $ flash_recovery_area_usage;
The usage of each part is clearly displayed in the output result.
Since the archive is put here, it is easy to do, just change the retention policy for deleting the archive script directly. But what should I do if I can't change it but expand the space? Below is my experiment and I hope it will be useful.
Select * from v $ flash_recovery_area_usage;
View usage:
Select sum (percent_space_used) x 300/100 from v $ flash_recovery_area_usage;
My size is 300 GB, of course, * 300, depending on the actual situation!
Modify db_recovery_file_dest_size:
Alter system set db_recovery_file_dest_size = 300G scope = both;
Close Database
Shutdown immediate
Restart:
Startup
That's all!
Oracle ORA-01555 snapshot old description
Troubleshooting for ORA-01078 and LRM-00109
ORA-01555 ultra-long Query Duration time
Notes on ORA-00471 Processing Methods
ORA-00314, redolog corruption, or missing Handling Methods
Solution to ORA-00257 archive logs being too large to store