Re: Oracle Standby and RAMN CATALOG
- From: Outsider <mufc01666@xxxxxxxxx>
- To: Guenadi Jilevski <gjilevski@xxxxxxxxx>
- Date: Fri, 4 Oct 2013 13:07:40 +0200
Guenadi,
Sorry I didn't understood this question.
Is the tnsnames alias, that rman is complaining about, on
the rman hosts tnanames.ora?
and
yes problem exists without auxiliary connect
~> rman target / catalog XXX/XXX@XXX
Recovery Manager: Release 11.2.0.3.0 - Production on Fri Oct 4 13:05:42 2013
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights
reserved.
rconnected to target database: XYZS1 (DBID=3537003386)
econnected to recovery catalog database
RMAN> sync 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/04/2013
13:05:48
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
RMAN>
thanks
*-----------------*
*Tiran*
*Best Regards
Stay in touch...*
On 4 October 2013 12:34, Guenadi Jilevski <gjilevski@xxxxxxxxx> wrote:
> Hi,
>
> Could you please look at the following:
>
> Is the tnsnames alias, that rman is complaining about, on the rman hosts
> tnanames.ora?
> Will the problem persist if you connect only to a target and catalog
> without connection to the auxiliary?
>
> Best Regards,
>
>
> On Fri, Oct 4, 2013 at 1:21 PM, Outsider <mufc01666@xxxxxxxxx> wrote:
>
>> Hi Guenadi,
>>
>> Yes they are configured....
>>
>> RMAN
>>
>> CONFIGURE DB_UNIQUE_NAME 'XYZS1DG1' CONNECT IDENTIFIER "XYZSIDG1";
>> CONFIGURE DB_UNIQUE_NAME 'XYZS1DG2' CONNECT IDENTIFIER "XYZSIDG2";
>>
>>
>> *-----------------*
>> *Tiran*
>> *Best Regards
>> Stay in touch...*
>>
>>
>> On 4 October 2013 12:14, Guenadi Jilevski <gjilevski@xxxxxxxxx> wrote:
>>
>>> 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
Other related posts:
