Shulou(Shulou.com)05/31 Report--

This article will explain in detail what to do about RMAN-06820 ORA-17629 errors in the database. The editor thinks it is very practical, so I share it for you as a reference. I hope you can get something after reading this article.

Make a database backup in the standby database as follows:

Oracle@node1:~ > rman target /

Recovery Manager: Release 11.2.0.4.0-Production on Thu Jun 4 06:45:04 2015

Copyright (c) 1982, 2011, 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 current 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

If there is an error in the red font when performing a database backup in the standby database, the official method is as follows (after testing, the master and standby database should set the same password, otherwise there will be the same problem)

RMAN-06820 ORA-17629 During Backup at Standby Site (document ID 1616074.1)

In this Document

SymptomsChangesCauseSolutionReferences

APPLIES TO:Oracle Database-Enterprise Edition-Version 11.2.0.4 and later

Information in this document applies to any platform.

SYMPTOMS

RMAN archivelog backup at the standby site is 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 current 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

CHANGES

Database was upgraded to 11.2.0.4

CAUSE

Per 'unpublished' Bug 8740124, 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.

However, the connection to the primary failed when attempting to do so.

This is due to this bug:

Bug 17580082-ACTIVE STANDBY-RMAN-06820: WARNING: FAILED TO ARCHIVE CURRENT LOG AT PRIMARY

SOLUTION

Workaround

Do not use operating system authentication to login with RMAN. Use a username and password.

That is, do 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 CURRENT LOG AT PRIMARY

NOTE:8740124.8-Bug 8740124-Current standby redo log group should be included in the database backup by RMAN

NOTE:1301769.1-ORA-17629: this is the end of RMAN Resync Catalog from db_unique_name all fails's article on "what to do if there are RMAN-06820 ORA-17629 errors in the database". I hope the above content can be of some help to you, so that you can learn more knowledge. if you think the article is good, please share it for more people to see.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.