RMAN DELETE ARCHIVELOG Command Takes Long Time to Complete

郑全

RMAN DELETE ARCHIVELOG Command Takes Long Time to Complete (文档 ID 1589307.1)
转到底部

In this Document
Symptoms
Changes
Cause
Solution
References

Applies to:
Oracle Database - Enterprise Edition - Version 11.2.0.2.0 and later
Information in this document applies to any platform.
Symptoms
- RMAN delete archivelog command takes a very long time.
- Debug trace shows the time is being spent on call to refreshAgedFiles:
DBGMISC:       Executing command REFAF [15:32:26.218] (krmiexe)
..
DBGPLSQL:      channel default: Starting refreshAgedFiles at 26-sep-13 15:32:26 [15:32:26.236] (refreshAgedFiles)
DBGMISC:      EXITED krmiexe with status 0 [17:11:02.377] elapsed time [00:01:38:36.158]
DBGMISC:      Finished REFAF at 26-sep-13 17:11:02 [17:11:02.377]   <======== 1:39 mins
DBGMISC:     EXITED krmice [17:11:02.377] elapsed time [00:01:38:36.181]
DBGMISC:     ENTERED krmkmrsr [17:11:02.377]

- Problem SQL is:

SQL>SELECT :B7 TYPE_CON, OFFR.RECID KEY_CON, OFFR.RECID RECID_CON, OFFR.STAMP
STAMP_CON, TO_NUMBER(NULL) SETSTAMP_CON, TO_NUMBER(NULL) SETCOUNT_CON,
TO_NUMBER(NULL) BSRECID_CON, TO_NUMBER(NULL) BSSTAMP_CON, TO_NUMBER(NULL)
BSKEY_CON, TO_NUMBER(NULL) BSLEVEL_CON, TO_CHAR(NULL) BSTYPE_CON,
TO_NUMBER(NULL) ELAPSESECS_CON, TO_NUMBER(NULL) PIECECOUNT_CON,
TO_CHAR(NULL) FILENAME_CON, TO_CHAR(NULL) TAG_CON, TO_NUMBER(NULL)
COPYNUMBER_CON, TO_CHAR(NULL) STATUS_CON, TO_NUMBER(NULL) BLOCKS_CON,
...etc

Changes

Cause
Bug 14482635 : RMAN BACKUP IS TAKING LONG TIME WHEN FLASH RECOVERY AREA IS ENABLED


Solution
Bug 14482635  has been suspended as the requested information was not provided by client to debug it further
- The workaround is to use a RULE hint:
RMAN>sql "alter session set optimizer_mode=RULE";
RMAN>delete....



References
BUG:14482635 - RMAN BACKUP IS TAKING LONG TIME WHEN FLASH RECOVERY AREA IS ENABLEDb