ORACLE DB STARTUP TIME FULL

RMAN> backup archivelog all delete input You do that using RMAN, not SQLPLUS or ADRCI. The proper fix is to get rid of the recovery files. Now, you can shutdown and startup again and that previous error should be gone. Now, you can increase your current db_recovery_file_dest_size, increased to 75G in my case: SQL> alter system set db_recovery_file_dest_size = 75G scope=both Now, go into sqlplus without opening the database, just mounting it (you may be able to do this without mounting the database, but I mount it anyway). The quick and dirty one is to increase db_recovery_file_dest_size. There are two solutions, the proper one and the quick and dirty one. By design, if anything is messed up, Oracle will respond by shutting down.

ORACLE DB STARTUP TIME FULL

Once that is full (50GB full in this case). If you do push a lot of data into it, it saves transaction logs. In my case, the first error was: ORA-19815: WARNING: db_recovery_file_dest_size of 53687091200 bytes is 100.00% used, and has 0 remaining bytes available. Any errors after the first error are likely being caused by the first error. At least you can tail (and I hope you have a scrollback buffer): adrci> show alert -tail 100 Just stop wanting and deal with this interface. It would be very nice if they were in /var/log so you could easily parse the logs. You need to see the homes so you can connect to the one that you use. You have to run an Oracle log reading program: $ adrciĪDRCI: Release 11.2.0.1.0 - Production on Wed Sep 11 18:27:56 2013Ĭopyright (c) 1982, 2009, Oracle and/or its affiliates. Step 1: You need to look at the alert log. To do any of this, you must be the oracle user: $ su - oracle I am documenting it here in case someone else has this problem. After hours of misdirection from official Oracle support, I dove into this on my own and fixed it.

Oracle db startup time