LLI Wiki — My Digital Knowledge Base

ORA-03113 at startup: full recovery area

Find the first error in the alert log with ADRCI, then handle a full Oracle recovery area.

An Oracle database may fail at startup with ORA-03113: end-of-file on communication channel. This message does not give the cause: the alert log has to be read. This procedure (Oracle 11.2) shows how to find it with ADRCI, then how to handle a full recovery area.

Run all commands as the oracle user.

su - oracle

1. Read the alert log with ADRCI

The alert log is not in /var/log. It is read with ADRCI, inside the ADR (ADR base).

adrci

List the homes, then select the database home:

adrci> show homes
ADR Homes:
diag/rdbms/orcl/ORCL
diag/tnslsnr/orcl/listener

adrci> set home diag/rdbms/orcl/ORCL

Display the last lines of the alert log:

adrci> show alert -tail 100

Scroll back to the first error: the errors that follow are often caused by it. In the example, 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.

2. Understand the cause

The fast recovery area is full. Archived logs accumulate there; once the area is saturated, the database cannot start.

3. Quick fix: increase the recovery area size

Exit ADRCI, then mount the database without opening it:

sqlplus /nolog
SQL> connect / as sysdba
SQL> startup mount
SQL> alter system set db_recovery_file_dest_size = 75G scope=both;
SQL> shutdown
SQL> startup

The size (75G) is an example. This method only postpones the problem.

4. Proper fix: remove the archived logs with RMAN

rman target /
RMAN> backup archivelog all delete input;

If RMAN returns RMAN-06171: not connected to target database, run rman target / instead of rman.

Wait for the command to finish. The archived logs are backed up and then deleted, which frees the space. Then restart the database.

Notes

Mastodon LLIMastodon SocialFosstodon