Skip to main content

resyncing from database with DB_UNIQUE_NAME RMAN-03014: implicit resync of recovery catalog failed


There has been a structural changes on the primary DB ( like adding of data files,etc) and during the time, tried to connect from standby database using rman as below

rman target / catalog rman/rman@dbcat

 Recovery Manager: Release 11.2.0.4.0 - Production on Mon Oct 21 13:30:38 2019

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

 connected to target database: SPROD (DBID=1981104798)
connected to recovery catalog database
RMAN> show all;
2> ;

 ORA-20079: full resync from primary database is not done

 doing automatic resync from primary
resyncing from database with DB_UNIQUE_NAME SPROD
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of show command at 10/21/2019 11:00:29
RMAN-03014: implicit resync of recovery catalog failed
RMAN-03009: failure of partial resync command on default channel at 10/21/2019 11:00:29
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

 rman tries to resync the standby from primary using db_unique_name.

 However, RMAN is unable to connect to the primary because no connect string was used when connecting to the standby - 

 in order to resync from another host in a Data Guard configuration , the connection to target must be made with a username, password and alias.  

 This is documentation Bug 13774434: ORA-17629, ORA-17628 DURING RESYNC CATALOG FROM DB_UNIQUE_NAME ALL;
SoLUTION
Use a TNS connect string when connecting to the standby eg

 rman target sys/sys123@primary_db catalog rman/rman@dbcat
RMAN> show all;

 RMAN configuration parameters for database with db_unique_name SPRODSMU are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 2 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK;

CONFIGURE CONTROLFILE AUTOBACKUP ON;


Comments

Post a Comment

Popular posts from this blog

12.1.0 Grid Installation on Solaris 11.3 fails with ASM failed to start

Issue Description  We faced one issue, while installing the GI 12.1.0.1.0 on Solaris 11.3  ASM failed to start. Check /u01/app/grid/cfgtoollogs/asmca/asmca-201202PM061908.log for details. 2020/12/02 18:19:17 CLSRSC-184: Configuration of ASM failed 2020/12/02 18:19:17 CLSRSC-258: Failed to configure and start ASM Died at /u01/app/12.1.0/grid_1/crs/install/crsinstall.pm line 1976. The command '/u01/app/12.1.0/grid_1/perl/bin/perl -I/u01/app/12.1.0/grid_1/perl/lib -I/u01/app/12.1.0/grid_1/crs/install /u01/app/12.1.0/grid_1/crs/install/rootcrs.pl ' execution failed This error is coming during root.sh execution on primary node. After checking the asmca logs, the error seen is as below: ========================== [main] [ 2020-12-02 17:00:49.575 AST ] [UsmcaLogger.logException:156] SEVERE:method oracle.sysman.assistants.usmca.backend.USMInstance:configureLocalASM [main] [ 2020-12-02 17:00:49.575 AST ] [UsmcaLogger.logException:157] ORA-27122: unable to protect memory [main] [ 2020-1...
Post a Comment
Read more

Health Check Script

Oracle Database Health Check Script Run this script has sysdba user or any user having DBA Role Change the spool file patch to correct directory. In this example it is set to  /export/home/oraprod/ $ cat Health_Check_Script.sql set pagesize 1100 SET MARKUP HTML ON SPOOL ON spool /export/home/oraprod/health_check_new.html set feedback off set linesize 200; set pages 50 set lines 1000 set pages 70 set heading on PROMPT================================================================ prompt PROMPT PROMPT Daily_Monitoring Checkup Report prompt ================================================================================================================================================= PROMPT REPORT DATE select to_char(sysdate,'DD-MON-YYYY:HH:MI:SS') "Report Run Date" from dual; prompt DATABASE NAME PROMPT ============== select instance_name,host_name,version,status from gv$instance ,v$database a; PROMPT DATABASE INFO PROMPT =============...
1 comment
Read more

12.2 Stage area creation fails with startCD/Disk1/rapidwiz/bin/../jre/Linux_x64/1.6.0/bin/java: No such file or directory

 12.2 Stage area creation fails with startCD/Disk1/rapidwiz/bin/../jre/Linux_x64/1.6.0/bin/java: No such file or directory While creating the stage area for 12.2 Installation, we face issue while running the buildstage.sh ....startCD/Disk1/rapidwiz/bin/../jre/Linux_x64/1.6.0/bin/java: No such file or directory Solution:  Please go to the path provided in the error log and check if the java is working fine with below command: java -version Generally this java is having some issues.   Install the jre 7 or jre 8 and copy the the jre at the same path by renaming old folder. It should work fine.  Now if your run the build command again, it should succeed.  Running command: /u01/soft/ebs/startCD/Disk1/rapidwiz/bin/../jre/Linux_x64/1.6.0/bin/java -classpath /u01/soft/ebs/startCD/Disk1/rapidwiz/bin/../jlib/emocmutl.jar:/u01/soft/ebs/startCD/Disk1/rapidwiz/bin/../jlib/ewt-3_4_22.jar:/u01/soft/ebs/startCD/Disk1/rapidwiz/bin/../jlib/share-1_1_18.jar:/u01/soft/ebs/star...
Post a Comment
Read more