(RA20) SBT_RECOVERY_WINDOW value on Upstream Recovery Appliance May Negatively Impact the RECOVERY_WINDOW_GOAL on the Downstream Recovery Appliance

Asset ID:	1-77-2275933.1
Update Date:	2017-06-16
Keywords:

Solution Type Sun Alert Sure

Solution 2275933.1 : (RA20) SBT_RECOVERY_WINDOW value on Upstream Recovery Appliance May Negatively Impact the RECOVERY_WINDOW_GOAL on the Downstream Recovery Appliance

Applies to:

Zero Data Loss Recovery Appliance X4 Hardware - Version All Versions to All Versions [Release All Releases]
Zero Data Loss Recovery Appliance X6 Hardware - Version All Versions to All Versions [Release All Releases]
Zero Data Loss Recovery Appliance X5 Hardware - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.
Zero Data Loss Recovery Appliance Software - Version 12.1.1.1.7 and later

Description

Oracle has discovered a new critical issue for Recovery Appliance 12.1.1.1.7 and Recovery Appliance 12.1.1.1.8. The critical issue applies when all of the following are true:

Recovery Appliance replication is configured
Protection policies for databases configure for replication on the upstream Recovery Appliance have SBT_RECOVERY_WINDOW value that are less than the RECOVERY_WINDOW_GOAL value in the corresponding protection policies on the downstream Recovery Appliance. This applies to use of the pre-configured or user-configured policies.

If these are true, the upstream appliance incorrectly applies the SBT_RECOVERY_WINDOW to replicated backups on the downstream appliance, deleting backups that are required to satisfy RECOVERY_WINDOW_GOAL on the downstream Recovery Appliance.

Occurrence

Due to bug 26197946, RMAN database backups can be deleted prematurely. The result is compromised recovery window on the downstream Recovery Appliance.

Symptoms

The impact of this critical issue can result in the following:

RMAN Backups on the downstream Recovery Appliance to be incorrectly deleted from both disk and if present, tape backups on the downstream Recovery Appliance.

Workaround

If the upstream Recovery Appliance is not configured for a Media Manager, then on the upstream Recovery Appliance protection policies used for replication, set SBT_RECOVERY_WINDOW to NULL or in EM, clear the Media Manager Recovery Window Goal field.

If the upstream Recovery Appliance is configured with a Media Manager, then on the downstream Recovery Appliance protection policies used for the replicated backups, set ALLOW_BACKUP_DELETION to 'NO' or in EM, clear the "Backup Deletion" checkbox.

A side effect of implementing the second workaround is that the upstream Recovery Appliance will start to generate incidents with an error code of ORA-64766. The error can be seen in the RA_INCIDENT_LOG as well as in the Alert Log of the upstream Recovery Appliance, and the full error text reads

ORA-12012: error on auto execute of job "RASYS"."RA$_PURGE_SBT_3469580"
ORA-19509: failed to delete sequential file, handle="RA_SBT_430538_7truvnem_1_2_1735627", parms=""
ORA-27027: sbtremove2 returned error
ORA-19511: non RMAN, but media manager or vendor specific failure, error text:
KBHS-01404: See trace file /u01/app/oracle/product/12.1.0.2/dbhome_1/rdbms/log/sbtio_315562_139824020619904.log for details
KBHS-00719: Error 'recovery appliance Error'; ORA-64766: backup deletion using RMAN prevented by protection policy
ORA-45199: Error ORA-64766: backup deletion using RMAN prevented by protection policy
ORA-06512: at "RASYS.DBMS_RA_STORAGE", line 2954
ORA-06512: at line 1
encountered when executing begin dbms_ra_storage.free_backup_piece( p_dbkey => :db_key, p_piecename => :fname, p_ftype => DBMS_RA_INT.KBRSCHKTYPE_FILE, p_fincarn => :pieceinc, p_can_defer => TRUE, p_check_prot => TRUE); dbms_ra_scheduler.release_blocked_tasks( dbms_ra_sched

These incidents can be identified using the SQL statement

select incident_id,component,severity,status from ra_incident_log where status = 'ACTIVE' and parameter in ( select parameter from ra_incident_log where error_text like '%ORA-64766: backup deletion using RMAN prevented by%' )

The incidents can be reset using the Recovery Appliance API, dbms_ra.reset_error. For ease, the incidents can be reset using the PL/SQL block

begin
for incident in ( select incident_id,component,severity,status from ra_incident_log where status = 'ACTIVE' and parameter in ( select parameter from ra_incident_log where error_text like '%ORA-64766: backup deletion using RMAN prevented by%' ) )
loop
dbms_ra.reset_error(incident.incident_id);
end loop;
end;
/

Patches

None

History

12-JUN-2017 - Created

16-JUN-2017 - Published

Attachments

This solution has no attachment