Insufficient archive space ORA-00257 archiver error. Connect internal only, until freed solution

First check whether the disk space is normal, you can refer to the oracle trace cleanup

 

ORA-00257: archiver error. Connect internal only, until freed solution

1. Increase the maximum space

1.登录，sqlplus uposweba/uposweba@BOSSDB as sysdba

2. Check whether the archive log is enabled, archive log list

3. Enter rman, rman target web_db/web_db1234@BOSSDB

4. Modify the maximum space of the archive log, alter system set db_recovery_file_dest_size=35G 

 

 

oracle clean archive log (cache)

1. Use RMAN to connect to the target DB:

　　rman target /

　　RMAN target sys/*****@orcl

2. In the RMAN command window, enter the following command (clean up all archive logs):

　　crosscheck archivelog all;-check the archive log

　　delete expired archivelog all;-delete expired log

　　DELETE ARCHIVELOG ALL COMPLETED BEFORE'SYSDATE-7'; (specify to delete archive logs 7 days ago);

　　DELETE NOPROMPT ARCHIVELOG UNTIL TIME "TO_DATE('XXXX-XX-XX','YYYY-MM-DD')";

3. Other related commands:

　　list archivelog all; --View the archive log list:

　　list expired archivelog all;-view the list of expired archivelogs:

4. Clear archivelog regularly:

　　You can write the following code as a .bat file, and add a new timed task under the task plan of the control panel:

　　RMAN target sys/*****@orcl

　　crosscheck archivelog all；

　　delete expired archivelog all；