When this problem encountered, I did not look at the alarm log, always thought that the database lock blocking affects performance. Know that the archive log is full when the view log is found. To cause this problem to occur:
Errors in File/dbbk/oracle/diag/rdbms/orcl/orcl/trace/orcl_arc0_28918.trc:ora-19809:limit exceeded for recovery Filesora-19804:cannot Reclaim 34764800 bytes disk space from 4070572032 limitarc0:error 19809 Creating Archive log file To '/dbbk/oracle/flash_recovery_area/orcl/archivelog/2015_03_11/o1_mf_1_574_%u_.arc ' Wed Mar 14:55:13 2015Errors In File/dbbk/oracle/diag/rdbms/orcl/orcl/trace/orcl_arc1_28920.trc:ora-19815:warning:db_recovery_file_dest_size of 4070572032 bytes is 99.51% used, and have 20086784 remaining bytes available.
Prompted to manipulate the size of the archive area, delete the physical archive, clean up the expired archive through the Rman tool, presumably because the archive has been written, and the way through Rman is not very smooth. After the manual removal of the physical archive of history after a while, SQLPLUS, Rman and other tools to normal use. There are two things you need to do at this point. Redefine the size of the archive space and delete outdated and useless archives:
rman> Delete Expired Archivelog; Sql> alter system set db_recovery_file_dest_size=21474836480 Scope=both;
After these operations, the database can be used normally.
This article is from the "linuxoracle" blog, make sure to keep this source http://onlinekof2001.blog.51cto.com/3106724/1619383
Oracle Archive log full causes database performance to be unusually slow