How is the tnsnames and listener files configured on the recovery catalog? Date: Fri, 4 Oct 2013 11:39:16 +0200 Subject: Re: Oracle Standby and RAMN CATALOG From: mufc01666@xxxxxxxxx To: chinedui@xxxxxxxxxx; dedba@xxxxxxxxxx; oracle-l@xxxxxxxxxxxxx Dear Chinedu, Everything is configured like you said. And strange is that this works about 6 months. ----------------- TiranBest Regards Stay in touch... On 4 October 2013 09:28, Ndidi Ibeachum <chinedui@xxxxxxxxxx> wrote: Dear Tiran; I have come across a similar problem before. For this to work, A tnsnames entry should be present in each database for connection both ways ie. a tns names entry from the standby to the primary and vice versa. In addition, configure a static listener on both nodes to stand in for the tns entries. Try and feedback. Cheers Chinedu > Date: Wed, 2 Oct 2013 12:30:40 +0200 > Subject: Oracle Standby and RAMN CATALOG > From: mufc01666@xxxxxxxxx > To: oracle-l@xxxxxxxxxxxxx > > 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. > > this is from my log from cron > > ORA-20079: full resync from primary database is not done > > doing automatic resync from primary > > resyncing from database with DB_UNIQUE_NAME XYZS1DG1 > > RMAN-00571: =========================================================== > > RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== > > RMAN-00571: =========================================================== > > RMAN-03002: failure of configure command at 10/02/2013 04:00:18 > > RMAN-03014: implicit resync of recovery catalog failed > > RMAN-03009: failure of partial resync command on default channel at > > 10/02/2013 04:00:18 > > 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 > > > I tried to connect via RMAN to catalog and it works. > > #:~> rman target / catalog XXX/XXX@XXX > > Recovery Manager: Release 11.2.0.3.0 - Production on Wed Oct 2 12:24:05 2013 > > Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights > > reserved. > > connected to target database: XYZS1 (DBID537003386) > > *connected to recovery catalog database* > > > but when I started resync > > RMAN> resync catalog; > > starting partial resync of recovery catalog > > ORA-20079: full resync from primary database is not done > > doing automatic resync from primary > > resyncing from database with DB_UNIQUE_NAME XYZS1DG1 > > RMAN-00571: =========================================================== > > RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== > > RMAN-00571: =========================================================== > > RMAN-03009: failure of resync command on default channel at 10/02/2013 > > 12:25:51 > > 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 > > > > How can be this possible ? I not connected to catalog database already ? or > I am missing something...... > > > What I did. > > I resync catalog from Primary database so Standby not need to resync it > again and my backup works well in night but this is only for 1 night. Next > day again some problem. > > Please help, advise. > > Thanks in advance. > > > *-----------------* > *Tiran* > *Best Regards > Stay in touch...* > > > -- > //www.freelists.org/webpage/oracle-l > > -- //www.freelists.org/webpage/oracle-l