Oracle DTC archive log backup fails with ORACLE DTC5
Problem description
Oracle DTC archive log backup fails with ORACLE_DTC5. Following are some of the points related to the archive log backup failure:
-
Not all database archive log backups will fail. The failure can occur in one database.
-
If there is only one database for backup which has the capture process enabled, then the backup will fail immediately.
-
This error can occur even if there is no expired archive log.
-
There can be either golden gate integrated captures or data guard, which still need those archive logs.
Cause
Oracle DTC archive log backup fails with ORACLE_DTC5 if the capture process is enabled.
Traceback
You get the following error in the Phoenix.log , main_service.log, and Rman.log files:
archived log file name=/u02/archive/<DatabaseName>/<DatabaseName>/archivelog/2021_09_08/o1_mf_1_16304_jmj9zok8_.arc thread=1 sequence=16304
RMAN-08137: warning: archived log not deleted, needed for standby or upstream capture process
Resolution
-
Upgrade the Oracle DTC agent to the latest version.
-
Disable the capture process.
Note : Consult your Oracle administrator before making any changes.
Verification
To check whether the capture process is enabled, run the following query:
SQL> select CAPTURE_NAME,QUEUE_OWNER,status from dba_capture;
CAPTURE_NAME QUEUE_OWNER STATUS
------------------ ------------------ --------
<DatabaseName> GGATE ENABLED
To disable the capture process, run the following procedure:
SQL> exec DBMS_CAPTURE_ADM.STOP_CAPTURE('<DatabaseName>');
PL/SQL procedure successfully completed.
To verify if the capture process is disabled, run the following query:
SQL> select CAPTURE_NAME,QUEUE_OWNER,status from dba_capture;
CAPTURE_NAME QUEUE_OWNER STATUS
------------------ ------------------ --------
<DatabaseName> GGATE DISABLED