Make a database backup of the standby database as follows:
[Email protected]:~> rman Target/
Recovery manager:release 11.2.0.4.0-production on Thu June 4 06:45:04 2015
Copyright (c) 1982, Oracle and/or its affiliates. All rights reserved.
Connected to target database:oracle (dbid=1753883584, not open)
Rman> Backup Database format '/home/oracle/fulldb_%u.bak ' plus archivelog format '/home/oracle/arch_%u.bak ' delete all input;
Starting backup at 04-jun-15
Using target database control file instead of recovery catalog
rman-06820:warning:failed to archive-log at primary database
ORACLE error from Target database:
Ora-17629:cannot connect to the remote database server
Ora-17627:ora-01017:invalid Username/password; Logon denied
Ora-17629:cannot connect to the remote database server
In the standby database to perform a database backup report such as red font error, the official treatment method is as follows (tested, the master repository should be set the same password, otherwise there is a problem)
650) this.width=650; "id=" Kmpgtpl:sd_r1:0:dv_rdoc:0:s13 "src=" Https://support.oracle.com/epmos/adf/images/t.gif " Width= "Ten" height= "style=" Border:none;/> |
RMAN-06820 ORA-17629 During Backup at Standby Site (document ID 1616074.1) |
|
|
650) this.width=650; "id=" Kmpgtpl:sd_r1:0:dv_rdoc:0:s23 "src=" Https://support.oracle.com/epmos/adf/images/t.gif " Width= "Ten" height= "5" style= "Border:none;"/>
In this Document
Applies to:oracle database-enterprise edition-version 11.2.0.4 and later Information in this document applies to any platform. SymptomsRMAN Archivelog Backup at the standby site was throws the following errors at the start of the job: Starting backup at 15-jan-2014 13:44:46 rman-06820:warning:failed to archive-log at primary database ORACLE error from Target database: Ora-17629:cannot connect to the remote database server Ora-17627:ora-01017:invalid Username/password; Logon denied Ora-17629:cannot connect to the remote database server
But the rest of the backup actually complete successfully: skipping archived log of thread 1 with sequence 607; already backed up skipping archived log of thread 1 with sequence 614; already backed up Channel t1:starting archived log backup set Channel t1:specifying archived log (s) in Backup set input archived log thread=1 sequence=678 recid=290 stamp=836919086 input archived log thread=1 sequence=679 recid=291 stamp=836919369 input archived log thread=1 sequence=680 recid=292 stamp=836919706 input archived log thread=1 sequence=681 recid=293 stamp=836919873 Channel t1:starting piece 1 at 15-jan-2014 13:44:52 Channel t1:finished piece 1 at 15-jan-2014 13:46:17 piece handle=log_thmdb_20140115_171228_1_1 tag=log_twmdb comment=api version 2.0,mms version 5.4.1.0 Channel T1:backup set complete, elapsed time:00:01:25 finished backup at 15-jan-2014 13:46:17 ChangesDatabase was upgraded to 11.2.0.4 CausePer ' unpublished ' Bug 8740124, as of 11.2.0.4, we now include the current standby redo log as part of a RMAN Archivelog b Ackup at the standby site. This was achieved by forcing a log-switch at the primary site.
However, the connection to the primary failed when attempting to doing so. This was due to this bug: Bug 17580082-active standby-rman-06820:warning:failed to ARCHIVE-LOG at PRIMARY
SolutionWorkaround Do not use the operating system authentication to login with RMAN. Use a username and password.
That is, does not use just the '/' (Operating system authentication) connect to the standby database: $ Rman Target/ Instead put in the username and password for the SYSDBA user:
$ Rman Sys/password
Referencesbug:17580082-active standby-rman-06820:warning:failed to ARCHIVE-LOG at PRIMARY
Note:8740124.8-bug 8740124-current Standby Redo log group should be included on the database backup by RMAN Note:1301769.1-ora-17629:rman Resync Catalog from Db_unique_name all fails |
This article is from "Technical achievement dream!" "Blog, be sure to keep this provenance http://dreamsanqin.blog.51cto.com/845412/1660296
RMAN-06820 ORA-17629 During Backup at Standby Site