Solutions for full ORA-00257 archiving logs

Token ),

In the previous blog we mentioned how to enable or disable Oracle's ARCHIVELOG mode (http://www.linuxidc.com/Linux/2014-10/108120.htm ),

V $ recovery_file_dest; v $ flash_recovery_area_usage; v $ version;

Directory of the archived log file, maximum value (set to 20 GB), and current usage value

We can see that the archived log usage is 3.84%, because I have deleted the archive LOG file. Before deleting an archive log, a number such as 99.46 indicates that most of the archive log space is used.

Therefore, log on to the rman program to delete archive logs.

Rman target sys/pass @ prjdbcrosscheck archivelog all; expired archivelog all; -- delete expired logs

Deep Analysis

Later, I thought that manual deletion was not a way to allow the system to automatically delete it. Later, a database backup script was created. The backup policy is as follows:

Perform backups of zero increments every week. Archive logs are backed up and archive logs are deleted.

Perform incremental 1 backup every day, archive logs are backed up along with, and archive logs expired are deleted.

Because I have not set the validity period of archive logs, all the previously archived logs will be deleted after Incremental backup is completed in the first step, which is equivalent to retaining only one day of archived logs. After you execute this backup policy, an error like ORA-00257 still appears. At this time, it is no longer a problem to simply delete the archive logs, because the current archive log directory is distributed for one day. To expand the archive log directory, see:

SQL; --- set the space used (), 20 GBSystem alteredSQL> show parameter db_recovery_file_dest; --- view the archive Log Path Limit

At this time, the maximum directory for archiving logs is 20 GB. Restart oralce again according to this setting.

Instance

Recently, historical data is being imported. I want to import 2 GB history records to my database, with millions of records inserted. At this time, the database is in the archive mode, and every insert operation is recorded in the archive log. The archived logs are full three hours after the historical import operation is performed. At this point, my problem arises. If the archive log is full, will the history import operations work properly? Whether data can be inserted into the database. After consulting with the company DBA, I will get a reply. If the archive mode is in full mode and the archive logs are full, my historical data import operations will be blocked, it is not necessary to import the archived logs until I clear the archived logs.

Install Oracle 11gR2 (x64) in CentOS 6.4)

Steps for installing Oracle 11gR2 in vmwarevm

Install Oracle 11g XE R2 In Debian