Hi, Can you look at RMAN configuration for db_unique_name configuration? If the primary and standby are configured with a connect string ( Oracle Net tnsnames aliases specified) you should not have this problem. Look at http://docs.oracle.com/cd/B28359_01/backup.111/b28273/rcmsynta010.htm for the configure db_unique_name <name> connect identifier synatax. Best Regards, Guenadi Jilevski On Fri, Oct 4, 2013 at 6:36 AM, De DBA <dedba@xxxxxxxxxx> wrote: > Hi, > > I've never seen this happen, but it looks to me that the connection that > fails is not to the catalog. I read it as RMAN is trying to connect to the > primary in order to resync the catalog, and that name (the primary) does > not resolve. Did you check that tnsnames.ora on the machine/home that you > are running RMAN from has an entry for the primary? The tns alias should be > the same as what is defined in log_archive_config on the standby, I imagine. > > Cheers, > Tony > > On 02/10/13 20:30, Outsider wrote: > > Dear experts, > > I have physical data guard implemented and I also scheduled the backup of > > database with cron on Linux to IBM tape. Everything was fine for about 6 > > months. > > few days ago I realized that backup is not performed from standby > database. > > After same investigation I found out that this is because RMAN from > standby > > DB wants to resync catalog but can't connect to catalog database which > is > > separate database. > > > > > <snip> > > -- > //www.freelists.org/webpage/oracle-l > > > -- //www.freelists.org/webpage/oracle-l