What if Oracle archive logs are full (ora-00257)? oracleora-00257

What if Oracle archive logs are full (ora-00257)? oracleora-00257

Oracle Database error ORA-00257: archiver error. Connect internal only, until freed, how to solve it? This problem is located when the archiving logs are full. We will share with you the specific solutions below.

Solution:

SQL> select * from V $ FLASH_RECOVERY_AREA_USAGE; -- view the usage of archive content
FILE_TYPE PERCENT_SPACE_USED PERCENT_SPACE_RECLAIMABLE NUMBER_OF_FILES
----------------------------------------------------------------------
CONTROLFILE 0 0 0
ONLINELOG 0 0 0
ARCHIVELOG 99.9 0 255
BACKUPPIECE 0 0 0
IMAGECOPY 0 0 0
FLASHBACKLOG 0 0 0

Note: it can be seen that the ARCHIVELOG log has reached 99.9%. Delete it!

SQL> quit

C: \ Documents ents and Settings \ Administrator> rman

RMAN> connect target system/myoracle @ orcl

Note: system is an oracle user, myoracle is the oracle user password, and orcl is the name SID of the connected database.

RMAN> crosscheck archivelog all;
RMAN> delete expired archivelog all;

Note: delete expired Archives

In this way, the archive file is deleted. Go to sqlplus to view the ARCHIVELOG log usage!

The second method is to increase the maximum size of the flash log file. As follows:

Copy codeThe Code is as follows:
Alter system set DB_RECOVERY_FILE_DEST_SIZE = 10g

The preceding processing method is used when an error occurs when the log is full. We recommend that you create a task to regularly Delete the log, as shown below:

Delete archivelog all completed before 'sysdate-7'; // DELETE the archive DELETE archive seven days ago from time 'sysdate-7'; // DELETE the archive FROM the past seven days

The above content is about Oracle archiving logs full (ora-00257) of the solution, I hope you like.