Database performance exception and slowness caused by full archiving of Oracle logs

Database performance exception and slowness caused by full archiving of Oracle logs

When the database performance is abnormal and slow due to full archiving of Oracle logs, I did not view the alarm log and thought it was because the lock blocking of the database affected the performance. The archived log is full only when you view the log. This problem occurs:
Errors in file/DBBK/oracle/diag/rdbms/orcl/trace/orcl_arc0_28918.trc:

ORA-19809: limit exceeded for recovery files

ORA-19804: cannot reclaim 34764800 bytes disk space from 4070572032 limit

ARC0: 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 11 14:55:13 2015

Errors in file/DBBK/oracle/diag/rdbms/orcl/trace/orcl_arc1_2891_trc:

ORA-19815: WARNING: db_recovery_file_dest_size of 4070572032 bytes is 99.51% used, and has 20086784 remaining bytes available.

The error message is displayed, indicating that the size of the archive area is reached. Delete the physical archive and use the RMAN tool to clear the expired archive. It is estimated that the archive is still being written, and The RMAN method is not smooth. After manually deleting the historical physical archive, tools such as SQLPLUS and RMAN can be used normally. At this time, we need to re-define the size of the archive space and delete expired and useless archive:
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.