ORA-00257: Archiver error. Connect internal only, until freed triggered by the m

Recommended for you: Get network issues from WhatsUp Gold. Not end users.
I always approach has been solved for the purpose to solve the problem, leading to some fuzzy concept is not clear.

First write down the solution.

SQL> select * from V$FLASH_RECOVERY_AREA_USAGE; FILE_TYPE    PERCENT_SPACE_USED PERCENT_SPACE_RECLAIMABLE NUMBER_OF_FILES
------------ ------------------ ------------------------- ---------------
CONTROLFILE                   0                         0               0
ONLINELOG                     0                         0               0
ARCHIVELOG                48.21 (this is almost full, at the time)                         0             306
BACKUPPIECE                   0                         0               0
IMAGECOPY                     0                         0               0
FLASHBACKLOG                .06                         0              11


Enter the RMAN execution
rman target  / 

Check out some useless archivelog
RMAN> crosscheck archivelog all;
Archiving delete expired
RMAN> delete expired archivelog all;


It was vague on the two concepts of delete obsolete and delete expired. But the concepts of report and crosscheck is somewhat unclear.

The following is the official document on crosscheck and expired

When the CROSSCHECK command is used to determine whether backups recorded in the repository still exist on disk or tape, if RMAN cannot locate the backups, then it updates their records in the RMAN repository to EXPIRED status. You can then use the DELETE EXPIRED command to remove records of expired backups from the RMAN repository. If the expired files still exist, then the DELETE EXPIRED command terminates with an error.

To delete expired repository records:
  1. If you have not performed a crosscheck recently, then issue a CROSSCHECK command. For example, issue:
    CROSSCHECK BACKUP; # checks backup sets and copies on configured channels
  2. Delete the expired backups. For example, issue:
    DELETE EXPIRED BACKUP;

The book, delete expired is to remove RMAN repository is marked as expired records. Below is delete obsolete explained
          The RMAN DELETE command supports an OBSOLETE option, which deletes backups that are obsolete, that is, no longer needed to satisfy specified recoverability requirements. You can delete files obsolete according to the configured default retention policy, or another retention policy that you specify as an option to the DELETE OBSOLETE command. As with other forms of the DELETE command, the files deleted are removed from backup media, deleted from the recovery catalog, and marked as DELETED in the control file.
         
          If you specify the DELETE OBSOLETE command with no arguments, then RMAN deletes all obsolete backups defined by the currently configured retention policy For example:
DELETE OBSOLETE;           You can also use the REDUNDANCY or RECOVERY WINDOW clauses with DELETE to delete backups obsolete under a specific retention policy instead of the configured default:
DELETE OBSOLETE REDUNDANCY = 3; DELETE OBSOLETE RECOVERY WINDOW OF 7 DAYS;
Delete obsolete is according to the backup strategy directly delete those obsolete backups.


The concept of REPORT
    For the analysis of the available backup and let your database to answer some important questions, such as:
          What documents need to backup?
          Which files do not resume operation?
          What backup is abandoned and can be deleted?
          Schema for a period of time before the physical database is how?
          At present what file has no backup?

    REPORT NEED BACKUP
Analysis of what data files in the following strategy need backup
REPORT UNRECOVERABLE
Analysis of what is required for the data files backup, because these documents to do some NOLOGGING operations, such as direct-path insert
 
REPORT NEED BACKUP RECOVERY WINDOW OFn DAYS
REPORT NEED BACKUP REDUNDANCYn             
REPORT NEED BACKUP DAYS = n                 Display N days archived redo log can be recovered using file backups
REPORT NEED BACKUP INCREMENTAL n           

 
RMAN> REPORT NEED BACKUP TABLESPACE TBS_3     Need backup of tablespace RMAN> REPORT UNRECOVERABLE;                            Need not operation recovery data file backup
RMAN> REPORT OBSOLETE;                                      Analysis of what abandoned files can be deleted.

RMAN> REPORT SCHEMA;        Display database data file information

REPORT SCHEMA AT TIME 'SYSDATE-14';     # schema 14 days ago
REPORT SCHEMA AT SCN 1000;              # schema at scn 1000
REPORT SCHEMA AT SEQUENCE 100 THREAD 1; # schema at sequence 100
   



 
Recommended from our users: Dynamic Network Monitoring from WhatsUp Gold from IPSwitch. Free Download

Posted by King at December 11, 2013 - 4:00 AM