4 Added assumptions.
source | link

Doing a LIST EXPIRED ARCHIVELOG and then a DELETE EXPIRED ARCHIVELOG should cause a new LIST EXPIRED ARCHIVELOG to not show any entries in most situations. Here are a few situations that could cause this to not be the case.

  1. If FORCE is not specified on the delete command then it follows the archived log deletion policy which determines when archived redo log files are eligible for deletion.

  2. The deletion policy does not apply to foreign archived redo log files, which are logs received by a logical standby database for a LogMiner session.

These possibilities are from this documentation. If neither is applicable then perhaps you are running into a bug and should open an SR with support.

I assume you are running commands like this:

   list expired archivelog all;
   crosscheck archivelog all;
   delete expired archivelog all;
   list expired archivelog all;

Perhaps the LIST EXPIRED entries are for items not being deleted by the specific delete command you are doing. For example, a DELETE EXPIRED BACKUP will not delete expired archivelogs or expired copies.

Since the problem is sporadic, you shouldn't be having the problem referenced in MOS Doc ID 1189883.1 in which the backup command follows the form backup archivelog all archivelog...

Doing a LIST EXPIRED ARCHIVELOG and then a DELETE EXPIRED ARCHIVELOG should cause a new LIST EXPIRED ARCHIVELOG to not show any entries in most situations. Here are a few situations that could cause this to not be the case.

  1. If FORCE is not specified on the delete command then it follows the archived log deletion policy which determines when archived redo log files are eligible for deletion.

  2. The deletion policy does not apply to foreign archived redo log files, which are logs received by a logical standby database for a LogMiner session.

These possibilities are from this documentation. If neither is applicable then perhaps you are running into a bug and should open an SR with support.

Perhaps the LIST EXPIRED entries are for items not being deleted by the specific delete command you are doing. For example, a DELETE EXPIRED BACKUP will not delete expired archivelogs or expired copies.

Since the problem is sporadic, you shouldn't be having the problem referenced in MOS Doc ID 1189883.1 in which the backup command follows the form backup archivelog all archivelog...

Doing a LIST EXPIRED ARCHIVELOG and then a DELETE EXPIRED ARCHIVELOG should cause a new LIST EXPIRED ARCHIVELOG to not show any entries in most situations. Here are a few situations that could cause this to not be the case.

  1. If FORCE is not specified on the delete command then it follows the archived log deletion policy which determines when archived redo log files are eligible for deletion.

  2. The deletion policy does not apply to foreign archived redo log files, which are logs received by a logical standby database for a LogMiner session.

These possibilities are from this documentation. If neither is applicable then perhaps you are running into a bug and should open an SR with support.

I assume you are running commands like this:

   list expired archivelog all;
   crosscheck archivelog all;
   delete expired archivelog all;
   list expired archivelog all;

Perhaps the LIST EXPIRED entries are for items not being deleted by the specific delete command you are doing. For example, a DELETE EXPIRED BACKUP will not delete expired archivelogs or expired copies.

Since the problem is sporadic, you shouldn't be having the problem referenced in MOS Doc ID 1189883.1 in which the backup command follows the form backup archivelog all archivelog...

3 added 4 characters in body; added 1 characters in body
source | link

Doing a LIST EXPIRED ARCHIVELOG and then a DELETE EXPIRED ARCHIVELOG should cause a new LIST EXPIRED ARCHIVELOG to not show any entries in most situations. Here are a few situations that could cause this to not be the case.

  1. If FORCE is not specified on the delete command then it follows the archived log deletion policy which determines when archived redo log files are eligible for deletion.

  2. The deletion policy does not apply to foreign archived redo log files, which are logs received by a logical standby database forafor a LogMiner session.

These possibilities are from this documentation. If neither is applicable then perhaps you are running into a bug and should open an SR with supportopen an SR with support.

Perhaps the LIST EXPIRED entries are for items not being deleted by the specific delete command you are doing. For example, a DELETE EXPIRED BACKUP will not delete expired archivelogs or expired copies.

Since the problem is sporadic, you shouldn't be having the problem referenced in MOS Doc ID 1189883.1 in which the backup command follows the form backup archivelog all archivelog...

Doing a LIST EXPIRED ARCHIVELOG and then a DELETE EXPIRED ARCHIVELOG should cause a new LIST EXPIRED ARCHIVELOG to not show any entries in most situations. Here are a few situations that could cause this to not be the case.

  1. If FORCE is not specified on the delete command then it follows the archived log deletion policy which determines when archived redo log files are eligible for deletion.

  2. The deletion policy does not apply to foreign archived redo log files, which are logs received by a logical standby database fora LogMiner session.

These possibilities are from this documentation. If neither is applicable then perhaps you are running into a bug and should open an SR with support.

Perhaps the LIST EXPIRED entries are for items not being deleted by the specific delete command you are doing. For example, a DELETE EXPIRED BACKUP will not delete expired archivelogs or expired copies.

Since the problem is sporadic, you shouldn't be having the problem referenced in MOS Doc ID 1189883.1 in which the backup command follows the form backup archivelog all archivelog...

Doing a LIST EXPIRED ARCHIVELOG and then a DELETE EXPIRED ARCHIVELOG should cause a new LIST EXPIRED ARCHIVELOG to not show any entries in most situations. Here are a few situations that could cause this to not be the case.

  1. If FORCE is not specified on the delete command then it follows the archived log deletion policy which determines when archived redo log files are eligible for deletion.

  2. The deletion policy does not apply to foreign archived redo log files, which are logs received by a logical standby database for a LogMiner session.

These possibilities are from this documentation. If neither is applicable then perhaps you are running into a bug and should open an SR with support.

Perhaps the LIST EXPIRED entries are for items not being deleted by the specific delete command you are doing. For example, a DELETE EXPIRED BACKUP will not delete expired archivelogs or expired copies.

Since the problem is sporadic, you shouldn't be having the problem referenced in MOS Doc ID 1189883.1 in which the backup command follows the form backup archivelog all archivelog...

2 added 835 characters in body; added 190 characters in body; added 15 characters in body; deleted 1 characters in body
source | link

Perhaps theDoing a LIST EXPIRED ARCHIVELOG entries are for items not being deleted by the specific delete command you are doing. For example,and then a DELETE EXPIRED BACKUPARCHIVELOG willshould cause a new LIST EXPIRED ARCHIVELOG to not delete expired archivelogs or expired copiesshow any entries in most situations. Here are a few situations that could cause this to not be the case.

  1. If FORCE is not specified on the delete command then it follows the archived log deletion policy which determines when archived redo log files are eligible for deletion.

  2. The deletion policy does not apply to foreign archived redo log files, which are logs received by a logical standby database fora LogMiner session.

These possibilities are from this documentation. If neither is applicable then perhaps you are running into a bug and should open an SR with support.

Perhaps the LIST EXPIRED entries are for items not being deleted by the specific delete command you are doing. For example, a DELETE EXPIRED BACKUP will not delete expired archivelogs or expired copies.

Since the problem is sporadic, you shouldn't be having the problem referenced in MOS Doc ID 1189883.1 in which the backup command follows the form backup archivelog all archivelog...

Perhaps the LIST EXPIRED entries are for items not being deleted by the specific delete command you are doing. For example, a DELETE EXPIRED BACKUP will not delete expired archivelogs or expired copies.

Doing a LIST EXPIRED ARCHIVELOG and then a DELETE EXPIRED ARCHIVELOG should cause a new LIST EXPIRED ARCHIVELOG to not show any entries in most situations. Here are a few situations that could cause this to not be the case.

  1. If FORCE is not specified on the delete command then it follows the archived log deletion policy which determines when archived redo log files are eligible for deletion.

  2. The deletion policy does not apply to foreign archived redo log files, which are logs received by a logical standby database fora LogMiner session.

These possibilities are from this documentation. If neither is applicable then perhaps you are running into a bug and should open an SR with support.

Perhaps the LIST EXPIRED entries are for items not being deleted by the specific delete command you are doing. For example, a DELETE EXPIRED BACKUP will not delete expired archivelogs or expired copies.

Since the problem is sporadic, you shouldn't be having the problem referenced in MOS Doc ID 1189883.1 in which the backup command follows the form backup archivelog all archivelog...

1
source | link