Not Able To Connect To DBaaS Instance As The Database Is Not Coming Up With ORA-19809 And ORA-19804 (Doc ID 2392086.1)

Last updated on APRIL 27, 2018

Applies to:

Symptoms

Not able to connect the Database instance.

Alert log shows following errors and instance goes down:

Tue Apr 24 12:25:50 2018
Errors in file /u01/app/oracle/diag/rdbms/orcl/ORCL/trace/ORCL_arc1_10141.trc:
ORA-19809: limit exceeded for recovery files
ORA-19804: cannot reclaim 924815360 bytes disk space from 53687091200 limit
ARC1: Error 19809 Creating archive log file to '/u03/app/oracle/fast_recovery_area/ORCL/archivelog/2018_04_24/o1_mf_1_22434_%u_.arc'
Tue Apr 24 12:25:50 2018
Errors in file /u01/app/oracle/diag/rdbms/orcl/ORCL/trace/ORCL_ora_10133.trc:
ORA-16038: log 2 sequence# 22433 cannot be archived
ORA-19809: limit exceeded for recovery files
ORA-00312: online log 2 thread 1: '/u04/app/oracle/redo/redo02.log'
Tue Apr 24 12:25:50 2018
USER (ospid: 10133): terminating the instance due to error 16038
Tue Apr 24 12:25:50 2018
System state dump requested by (instance=1, osid=10133), summary=[abnormal instance termination].
System State dumped to trace file /u01/app/oracle/diag/rdbms/orcl/ORCL/trace/ORCL_diag_10085_20180424122550.trc
Tue Apr 24 12:25:50 2018

- From df command we can see there is lot of space left in /u03 which hold FRA (archive logs).

- Following query from database (in mount mode) show the FRA is fully used by archive logs:

    SQL> select * from v$recovery_file_dest;

Changes

 Archive log files from FRA destination were removed manually at OS level.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.