Archiving cannot delete reported RMAN-8137 error troubleshooting Process

This error occurs when using RMAN to back up database archive logs, quot; RMAN-8137: WARNING: archivedlognotdeletedasitisstillneeded

This error occurs when using RMAN to back up database archive logs, quot; RMAN-8137: WARNING: archived log not deleted as it is still needed

This error occurs when you use RMAN to back up database archive logs, "RMAN-8137: WARNING: archived log not deleted as it is still needed ".

This is a prompt that the archive file operation failed after the archive log is backed up.

The script for deleting archive log files in RMAN backup is as follows:
Backup archivelog all format'/rman_bak/archivelog _ % U. % t' delete all input;

Here, the database system is Oracle 10.2.0.3, and two standby databases are configured to form a one-to-two data guard environment.

Analyze problems

This RMAN-8137 error occurs when archiving logs prompts that the archive log file is not applied in the standby library when RMAN tries to delete them, so it cannot be deleted. This is a mechanism to protect data guard.

Use the following SQL statement to check whether archive log files are applied.

Select thread #, sequence #, completion_time, APPLIED
From v $ archived_log
Where dest_id = 2
And applied = 'no'
And completion_time> sysdate-2
Order by thread #, SEQUENCE #, COMPLETION_TIME;

The results show that many archived logs have not been applied in the last two days.

No records were found when checking v $ archive_gap.

No errors were found when checking the data guard configuration environment. This error also occurs when the environment is initially run, because the initialization parameter configuration of standby is incorrect.

This error message is described in the brief configuration of Oracle Data Guard 10g.

Metalink prompt for Oracle, which may be a bug, see the document Archive Log not Getting Deleted Using Rman With Rman-08137 [ID 964522.1]
A solution is provided to forcibly Delete the archived log files that have been backed up.

Delete force archivelog until time 'trunc (sysdate-4) 'backed up 1 times to device type disk;

However, when I use this SQL statement to query the application of archived logs,
Select thread #, sequence #, completion_time, APPLIED
From v $ archived_log
Where dest_id = 2
-- And applied = 'no'
And completion_time> sysdate-2
Order by thread #, SEQUENCE #, COMPLETION_TIME;

THREAD # SEQUENCE # COMPLETION_TIME APPLIED
1 1 81516 11:17:11 NO
2 1 81517 11:18:12 YES
3 1 81518 11:19:15 YES

4 1 81519 11:20:15 NO

--------------------------------------------------------
6 1 81521 11:22:21 YES

--------------------------------------------------------
8 1 81523 11:24:25 YES
9 1 81524 11:25:25 NO
--------------------------------------------------------
19 1 81534 11:35:44 YES

The results show that some log files have applied YES and some have NO.
There is no solution. Apply is successful or failed.

For more information about Oracle, see the Oracle topic page? Tid = 12