RMAN-06613 Standby Db Not Switching Log On Primary Using Rman (Doc ID 2098273.1)

Last updated on AUGUST 29, 2017

Applies to:

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

Symptoms

DataGuard environment.

RMAN backup ran on Standby.
Standby can't switch log on the primary so wouldn't be able to use backups to recover primary db.

rman target sys/

Recovery Manager: Release 12.1.0.2.0 - Production on Tue Jan 5 09:33:58 2016

Copyright (c) 1982, 2014, Oracle and/or its affiliates.  All rights reserved.

target database Password:
connected to target database: EXBTPRD2 (DBID=1438234023, not open)

RMAN> RUN
{
 ALLOCATE CHANNEL c1 DEVICE TYPE DISK FORMAT "/ora/EXBTPRD2/export/rman_tst_%U";
 backup archivelog from sequence 8710;
}

using target database control file instead of recovery catalog
allocated channel: c1
channel c1: SID=1558 device type=DISK

Starting backup at 05-JAN-2016 09:34
Connect identifier for DB_UNIQUE_NAME exbtprd2_primary not configured
RMAN-06820: WARNING: failed to archive current log at primary database
specification does not match any archived log in the repository
backup cancelled because there are no files to backup
Finished backup at 05-JAN-2016 09:34
released channel: c1

 

rman.trc

-------------

DBGSQL: TARGET> begin :lprimary_db_cs := sys.dbms_backup_restore.get_connect_identifier (dbuname=> :primary_dbuname); end;
DBGSQL: sqlcode = 0
DBGSQL: B :lprimary_db_cs = NULL
DBGSQL: B :primary_dbuname = exbtprd2_primary
DBGRCVMAN: getConfig: configurations exists for this site
RMAN-06613: Connect identifier for DB_UNIQUE_NAME exbtprd2_primary not configured
RMAN-06820: WARNING: failed to archive current log at primary database

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