Oracle 10G on windows re-sync the "db_recovery_file_dest_size" wih the OS?
Is there a way to re-sync what Oracle sees as the "db_recovery_file_dest_siz
I have over 200GB of free space on my the D:\ drive of my windows server, yet every month or so Oracle will just shut off user connections and show the error of:
"ORA-00257: archiver error. Connect internal only, until freed."
I can clearly see there is enough disk space for Oracle to keep archiving, however it just stops.
Please help, this has become very frustrating.
I have over 200GB of free space on my the D:\ drive of my windows server, yet every month or so Oracle will just shut off user connections and show the error of:
"ORA-00257: archiver error. Connect internal only, until freed."
I can clearly see there is enough disk space for Oracle to keep archiving, however it just stops.
Please help, this has become very frustrating.
ASKER
I have 150GB as the value, I guess I will increase it to 200GB. I thought I heard an Oracle DBA talking about Oracle with WINDOWS and how, oracle and windows do not automatically synchronize. He was saying even if I delete every log file and every backup file from the "show parameter db_recovery_file_dest" directory, ORACLE will not recognize that the space is free until I run some command telling ORACLE to recheck the actual disk space. As luck would have it...I can't find that email, and I need that command. Any help would be greatly appreciated.....
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
OK, so as of right now I have 160 GB of free space on my D:\drive, however I am now getting the error of "ORA-00257: archiver error. Connect internal only, until freed.". Everything is on the D:\drive, I only have C and D. No oracle files exist on C:\.
I don't think the backups ran last night because of this issue. Please help me figure out what the root cause of this is. I don't know that could be causing this or what to do....
I don't think the backups ran last night because of this issue. Please help me figure out what the root cause of this is. I don't know that could be causing this or what to do....
ASKER
I am running these commands:
delete noprompt expired archivelog all;
delete noprompt obsolete;
delete noprompt expired backup;
Will that tell Oracle that there really is 160GB of free space. Thanks for all your help, I think the RMAN commands is what he told me to do last time.
delete noprompt expired archivelog all;
delete noprompt obsolete;
delete noprompt expired backup;
Will that tell Oracle that there really is 160GB of free space. Thanks for all your help, I think the RMAN commands is what he told me to do last time.
That should do it. However, if you delete all your archivelogs, make sure you take a full database backup immediately after that.
ASKER
Thank you sir! You were spot on, the RMAN stuff is exactly what I needed.
Glad to hear it all worked out!
In order to avoid running into this issue again, I would further suggest that you run periodical backups that delete the archivelogs (you can make a batch file which you can schedule to run at specific times in Windows Task Scheduler)
In order to avoid running into this issue again, I would further suggest that you run periodical backups that delete the archivelogs (you can make a batch file which you can schedule to run at specific times in Windows Task Scheduler)
As sys, run this:
> show parameter db_recovery_file_dest_size
That will tell you how much recovery space is set in Oracle. Check out this link for an explanation of this parameter:
http://www.ucertify.com/article/what-is-the-db_recovery_file_dest_size-initialization-parameter.html