CCtech
asked on
Oracle Recovery File Size
We have a program that works off of an oracle database. The program locks up and will stop functioning, due to the oracle file - db_recovery_file_dest c:\oracle\product\10.2.0\f lash growing to its max size.
Our workaround has been to use the command: SQL> alter system set db_recovery_file_dest_size =8G scope=both;
We have expanded the size from 2GB, to 4, to 6, and now to 8. Once we expand the log file max size, the program works again. The problem is obvious, that this is only a temporary workaround and we need a permanent fix to purge the file so we do not need to increase the size every time the program crashes.
Unfortunately we have product support, but they will not support the oracle side, so I am looking for a way to resolve this issue such as a script that will purge files that I can run as a weekly task, so it will keep the file from reaching it's max. Thanks in advance.
Our workaround has been to use the command: SQL> alter system set db_recovery_file_dest_size
We have expanded the size from 2GB, to 4, to 6, and now to 8. Once we expand the log file max size, the program works again. The problem is obvious, that this is only a temporary workaround and we need a permanent fix to purge the file so we do not need to increase the size every time the program crashes.
Unfortunately we have product support, but they will not support the oracle side, so I am looking for a way to resolve this issue such as a script that will purge files that I can run as a weekly task, so it will keep the file from reaching it's max. Thanks in advance.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
hiring a local freelance oracle dba might get you a lot further
there is a lot of vendors who "use" oracle for storing data
and some of those vendors don't actually know how oracle needs to be maintained
as they rely on the local freelance oracle dba to do that
this is because some companies require so many vendors for all sorts of application
that they decide to go for a dedicated oracle solution
or whatever list of specific databases they (and the vendors) choose
hiring a freelance oracle dba for a limited period (or recurring period) is something to look at
before having to call the oracle fire brigade after the disaster has happened
there is a lot of vendors who "use" oracle for storing data
and some of those vendors don't actually know how oracle needs to be maintained
as they rely on the local freelance oracle dba to do that
this is because some companies require so many vendors for all sorts of application
that they decide to go for a dedicated oracle solution
or whatever list of specific databases they (and the vendors) choose
hiring a freelance oracle dba for a limited period (or recurring period) is something to look at
before having to call the oracle fire brigade after the disaster has happened
ASKER
Thanks for the input. We are going to have an Oracle DBA work on this, as it is looking to be much more in depth then I had expected.
ASKER
We recently took over this client and are working to migrate to new vendor, but for now we are working with what we have.
The program is writing files to C:\oracle\product\10.2.0\f
I'm not sure if RMAN is in use, but we back up the server every hour, so any data on the server including these recovery files are backed up with our backup software (Datto).
I'm not sure if there is a retention policy that needs to be set to only keep a week or so instead of unlimited. If I navigate to C:\oracle\product\10.2.0\f