The best solution is a simple one.
Standard Edition Oracle with Manual Standby generating error – RMAN-06820.
From RMAN-06820 ORA-17629 During Backup at Standby Site (Doc ID 1616074.1):
As of 11.2.0.4, we now include the current standby redo log as part of an RMAN archivelog backup at the standby site.
This is achieved by forcing a log switch at the primary site.
Some options to remedy the issue which seems too complicated.
RMAN-06820 ORA-17629 ORA-12154 During Backup of a Standby Database (Doc ID 2025142.1)
OERR: RMAN-6613 “Connect identifier for DB_UNIQUE_NAME %s not configured” Reference Note (Doc ID 2050646.1)
RMAN-06613: Connect identifier for DB_UNIQUE_NAME not configured (Doc ID 1598653.1)
DEMO:
oracle@arrow2:HAWKB:/home/oracle $ rman target / Recovery Manager: Release 11.2.0.4.0 - Production on Thu Dec 1 14:09:07 2016 Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved. connected to target database: HAWK (DBID=3187737370, not open) RMAN> show all; using target database control file instead of recovery catalog RMAN configuration parameters for database with db_unique_name HAWKB are: CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default CONFIGURE BACKUP OPTIMIZATION ON; CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default CONFIGURE MAXSETSIZE TO UNLIMITED; # default CONFIGURE ENCRYPTION FOR DATABASE OFF; # default CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/11.2.0.4/db_1/dbs/snapcf_HAWKB.f'; # default RMAN> CONFIGURE DB_UNIQUE_NAME 'HAWKB' CONNECT IDENTIFIER 'HAWKB'; RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03002: failure of configure command at 12/01/2016 14:09:26 RMAN-05021: this configuration cannot be changed for a BACKUP or STANDBY control file RMAN> backup archivelog all not backed up 2 times tag='ALL'; Starting backup at 2016-DEC-01 14:09:53 RMAN-06820: WARNING: failed to archive current log at primary database ORACLE error from target database: ORA-17629: Cannot connect to the remote database server ORA-17627: ORA-00942: table or view does not exist allocated channel: ORA_DISK_1 channel ORA_DISK_1: SID=36 device type=DISK channel ORA_DISK_1: starting archived log backup set channel ORA_DISK_1: specifying archived log(s) in backup set input archived log thread=1 sequence=342 RECID=274 STAMP=929450567 input archived log thread=1 sequence=343 RECID=275 STAMP=929451468 input archived log thread=1 sequence=344 RECID=276 STAMP=929452365 input archived log thread=1 sequence=345 RECID=277 STAMP=929453265 input archived log thread=1 sequence=346 RECID=278 STAMP=929454166 input archived log thread=1 sequence=347 RECID=279 STAMP=929455067 channel ORA_DISK_1: starting piece 1 at 2016-DEC-01 14:09:54 channel ORA_DISK_1: finished piece 1 at 2016-DEC-01 14:09:55 piece handle=/fra/HAWKB/backupset/2016_12_01/o1_mf_annnn_ALL_d417xlg1_.bkp tag=ALL comment=NONE channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01 Finished backup at 2016-DEC-01 14:09:55 RMAN> backup archivelog until time 'sysdate' not backed up 2 times tag='UNTIL'; Starting backup at 2016-DEC-01 14:10:22 using channel ORA_DISK_1 channel ORA_DISK_1: starting archived log backup set channel ORA_DISK_1: specifying archived log(s) in backup set input archived log thread=1 sequence=342 RECID=274 STAMP=929450567 input archived log thread=1 sequence=343 RECID=275 STAMP=929451468 input archived log thread=1 sequence=344 RECID=276 STAMP=929452365 input archived log thread=1 sequence=345 RECID=277 STAMP=929453265 input archived log thread=1 sequence=346 RECID=278 STAMP=929454166 input archived log thread=1 sequence=347 RECID=279 STAMP=929455067 channel ORA_DISK_1: starting piece 1 at 2016-DEC-01 14:10:22 channel ORA_DISK_1: finished piece 1 at 2016-DEC-01 14:10:23 piece handle=/fra/HAWKB/backupset/2016_12_01/o1_mf_annnn_UNTIL_d417ygxb_.bkp tag=UNTIL comment=NONE channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01 Finished backup at 2016-DEC-01 14:10:23 RMAN> backup archivelog all not backed up 2 times tag='ALL'; Starting backup at 2016-DEC-01 14:10:26 RMAN-06820: WARNING: failed to archive current log at primary database ORACLE error from target database: ORA-17629: Cannot connect to the remote database server ORA-17627: ORA-00942: table or view does not exist using channel ORA_DISK_1 skipping archived logs of thread 1 from sequence 342 to 347; already backed up Finished backup at 2016-DEC-01 14:10:26 RMAN> backup archivelog until time 'sysdate' not backed up 2 times tag='UNTIL'; Starting backup at 2016-DEC-01 14:10:32 using channel ORA_DISK_1 skipping archived logs of thread 1 from sequence 342 to 347; already backed up Finished backup at 2016-DEC-01 14:10:32 RMAN> exit Recovery Manager complete. oracle@arrow2:HAWKB:/home/oracle $
Database Backup and Recovery User’s Guide (11.2)
Backing Up Archived Redo Logs with RMAN
https://docs.oracle.com/cd/E11882_01/backup.112/e10642/rcmbckba.htm#BRADV81399
Online Redo Log Switch will occur with backup contains the following clause:
PLUS ARCHIVELOG
ARCHIVELOG ALL
ARCHIVELOG FROM ..
The simple solutions for not switching redo at primary.
Use backup archivelog until time ‘sysdate’ instead of backup archivelog all.
Use backup until sequence instead of from sequence.
Use backup database followed with backup archivelog until time ‘sysdate’.
UPDATE based on comments:
Using RMAN with sys password did not work. This test was not done by me but a teammate and I did not wanted to waste more of client’s time on the matter.
Recovery Manager: Release 11.2.0.4.0 - Production on Thu Nov 24 07:43:11 2016
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
RMAN> connect target sys
target database Password:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-12001: could not open channel default
RMAN-10008: could not create channel context
RMAN-10002: ORACLE error: ORA-15021: parameter "remote_dependencies_mode" is not valid in asm instance
RMAN-10006: error running SQL statement: alter session set remote_dependencies_mode = signature
RMAN> exit
Recovery Manager: Release 11.2.0.4.0 - Production on Thu Nov 24 07:43:36 2016
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
RMAN> connect target sys
target database Password:
connected to target database: PROD (DBID=4122225506, not open)
RMAN> BACKUP AS COMPRESSED BACKUPSET filesperset 20 maxsetsize 16G tag rman_PROD_AL_TEST ARCHIVELOG FROM SEQUENCE 47341;
Starting backup at 24-NOV-16
using target database control file instead of recovery catalog
RMAN-06820: WARNING: failed to archive current log at primary database
ORACLE error from target database:
ORA-17629: Cannot connect to the remote database server
ORA-17627: ORA-12154: TNS:could not resolve the connect identifier specified
ORA-17629: Cannot connect to the remote database server
allocated channel: ORA_DISK_1
Advertisements
