Archive log destination filling and Oracle's behaivor
I have a question regarding Oracle's behavior when the archive log destination filesystem fills. I noticed that if I purposely fill the archive log destination filesystem and then let Oracle run, even do some manual log switches, it says that the destination is unavailable, I even get an error when I attempt to login as a user, not / as sysdba. This is expected behavior. However, when I tail -f the alert log I see that I get the message saying that it can't archive a log and that it will keep retrying every 10 minutes. I read in the