This content has been marked as final. Show 1 reply
Its a tough question because internal Oracle sometimes wants more than it probably should. What I do is set it huge, but there are other options :
Stop using the db_recovery_file_dest by unsetting the parameter.
Remove the Entries from the rman repository/Controlfile ( In other words use RMAN to delete some archive you don't need despite your policy ) ( Delete files from recovery area using RMAN )
Consider changing RMAN archivelog deletion policy.
Consider changing RMAN retention policy.
Or - Increase the parameter db_recovery_file_dest_size - to a very large size.
How is the space pressure managed in the Flash Recovery Area - An Example. [ID 315098.1]
DUPLICATE WITHOUT TARGET FAILS WITH ORA-19809 BUT THERE IS FREE SPACE IN FRA [ID 1497894.1]
Edited by: mseberg on Nov 23, 2012 7:38 AM