The other day I had trouble getting our Oracle server (running on Redhat Enterprise) up and running. The only way we were able to get it working was to clear the log files under:
According to the manual they have to be cleared using the RMAN utility. What exactly are these files? Is there a way to control them?
The only kind of log file that would have to be managed by RMAN would be archived log files. Is the bdump directory your log archive destination (initialization parameter log_archive_dest or log_archive_dest_n)?
When the archiver process cannot archive a redo log (because of a full disk or any other reason), and the log writer tries to write to that log, the database will not permit further operations or connections until the archiver error is corrected. One way to prevent this is to use RMAN to back up your archived logs periodically, specifying the DELETE ALL INPUT option to delete the logs once they are backed up.
Dig Deeper on Oracle database performance problems and tuning
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.