ORA-00257archivererror-archiving failed due to full data flash back

ORA-00257: archivererror. Connectinternalonly, untilfreed ., After checking, I found that I was lazy and put the archived log location in the data

ORA-00257: archiver error. Connect internal only, until freed ., After checking, I found that I was lazy and put the archived log location in the data

ORA-00257 archiver error -- archiving failed due to full data flash back

System: Windows Server 2008 R2

Database Version: Oracle 10.2.0.4

This morning, an error occurred at work:

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

Database status: enabled but unavailable.

Alarm log:

~ Errors in file d: \ oracle \ product \ 10.2.0 \ admin \ orcl \ bdump \ orcl_arc1_3032.trc :~ The ORA-16038: log 3 sequence #87 cannot be archived ~ ORA-19809: limit exceeded for recovery files ~ ORA-00312: online log 3 thread 1: 'e: \ ORACLE10GRAC \ ORCL \ redo03.log '~

After checking, I found that I was lazy and put the archiving log location on the default location of the database, that is, the data flash back area, which has a space limit of 2 GB, archive logs are now 2 GB in size, so new archive logs cannot be generated, resulting in the above error.

There are many solutions:

Because my database is an OTLP online system that needs to provide services all the time, my initial thought was to immediately shut down the database, temporarily disable the archive mode, provide services first, and then solve the problem.

Run the command shutdown immediate, and the database remains unchanged. The reason should be that the clients are always connected. Therefore, in this close mode, the database cannot be closed because there is no active client, therefore, you can only shut down and restart the server to disconnect all clients.

After the server is started, shut down the database. When the database is enabled to the MOUNT mode, the archive mode is temporarily disabled:

Alter database noarchivelog;

Then shut down the database and restart the database. At this time, the database can be used.

For the archive mode, you can check the time when there are few connections on the client and set it again.

Three solutions:

Method 1: Disable the archive mode.

Method 2: increase the size of the flash back data Zone

Alter system set db_recovery_file_dest_size = 20G scope = both;

Method 3: Modify the location of the archived log.

Append:

Note that if the archiving log is located in the flash back area, you must pay attention to the capacity usage of the flash back area. You can view the v $ flash_recovery_area_usage view.

Select * from v $ flash_recovery_area_usage;