During backup of ARCHIVED redo logs on STANDBY, RMAN-06820: ORA-17631: WARNING: failed to archive current log at primary database

(Doc ID 2314136.1)

Last updated on OCTOBER 04, 2017

Applies to:

Oracle Database - Enterprise Edition - Version 12.1.0.2 and later
Information in this document applies to any platform.

Symptoms

RMAN-06820: WARNING: failed to archive current log at primary database
ORACLE error from target database:
ORA-17631: dbname 'me9sb' specified by remote server does not match the instance name 'e9pd'

STEPS
-----------------------

RMAN> CONFIGURE DEVICE TYPE DISK PARALLELISM 20 BACKUP TYPE TO COMPRESSED BACKUPSET;
2> CONFIGURE COMPRESSION ALGORITHM 'BASIC';
3> run
4> {
5> change archivelog all crosscheck;
6> change archivelog all validate;
7>
8> BACKUP INCREMENTAL LEVEL 0 SECTION SIZE 32G CUMULATIVE DEVICE TYPE DISK TAG 'WEEKLY' DATABASE;
9>
10> BACKUP DEVICE TYPE DISK TAG 'WEEKLY' ARCHIVELOG ALL NOT BACKED UP;
11>
12> DELETE NOPROMPT FORCE ARCHIVELOG ALL COMPLETED BEFORE 'sysdate-4';
13> }

Database backups have been raising warning RMAN-06820 and ora-17631 intermittently.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms