OraFAQ Forum: Data Guard » timeout with ARCH mode

Home » Server Options » Data Guard » timeout with ARCH mode

Show: Today's Messages :: Polls :: Message Navigator
E-mail to friend

timeout with ARCH mode [message #243021]

Tue, 05 June 2007 13:54

eldar52
Messages: 14
Registered: October 2005

Junior Member

Is there any option to define a network timeout for a ARCH process in a DG replication.

Because of the network problems to the standby database the ARCH may start working extremely slow and freeze the primary database because local archiving is not continuing.

Is there any option to dedicate one ARCH process to local archiving only ?

Thank you

Report message to a moderator

Re: timeout with ARCH mode [message #243317 is a reply to message #243021]

Wed, 06 June 2007 19:19

DreamzZ
Messages: 1666
Registered: May 2007
Location: Dreamzland

Senior Member

you can use the REOPEN caluse like this in example

ALTER SYSTEM SET LOG_ARCHIVE_DEST_2 = `SERVICE=prmy1 MANDATORY REOPEN=300';

Quote:

Use the REOPEN attribute of the LOG_ARCHIVE_DEST_n parameter to specify whether and when ARCn attempts to rearchive to a failed destination following an error. REOPEN applies to all errors, not just OPEN errors.

http://www.lc.leidenuniv.nl/awcourse/oracle/server.920/a96521/archredo.htm

Report message to a moderator

Re: timeout with ARCH mode [message #243502 is a reply to message #243317]

Thu, 07 June 2007 09:53

eldar52
Messages: 14
Registered: October 2005

Junior Member

Reopen does not solve the problem, because it works only if ARCH receives an error.
In our case over a slow WAN there are no errors , the log shipping is very slow.
I just wonder if there any timeout for ARCH (like we have for LGWR ) to stop the remote transfer and start the local archiving.
In 10g there is at least 1 ARCH process who is responsible for local archiving , is there any hidden parameter in 9i to implement this functionality ?

Report message to a moderator

Re: timeout with ARCH mode [message #243507 is a reply to message #243502]

Thu, 07 June 2007 10:07

DreamzZ
Messages: 1666
Registered: May 2007
Location: Dreamzland

Senior Member

I guess there is no such a option for archiving but search METALINK google and asktom.I guess in listener there is some option like that.

Report message to a moderator

Re: timeout with ARCH mode [message #244391 is a reply to message #243507]

Tue, 12 June 2007 10:24

eldar52
Messages: 14
Registered: October 2005

Junior Member

I would like to take advantage of the fact that the primary database is RAC in active/passive configuration.
Is there any option to define the passive instance in RAC to transfer the archive files of the both RAC instances ?

Thank you

Report message to a moderator

Re: timeout with ARCH mode [message #244407 is a reply to message #244391]

Tue, 12 June 2007 12:46

DreamzZ
Messages: 1666
Registered: May 2007
Location: Dreamzland

Senior Member

Quote:

Is there any option to define the passive instance in RAC to transfer the archive files of the both RAC instances ?

Your rac is running with single SPfile or Double pfiles?

Whats you mean Both RAC instances.

It generates only 1 archivelog per all instances i guess not indiviual per instance.

Report message to a moderator

Re: timeout with ARCH mode [message #244484 is a reply to message #244407]

Wed, 13 June 2007 01:34

eldar52
Messages: 14
Registered: October 2005

Junior Member

My both instances in RAC use the same spfile but i can define in the same spfile different parameters for each instance.
Like
INSTANCE1.log_archive_dest_2='SERVICE=REMOTE_DB LGWR ASYNC'
INSTANCE2.log_archive_dest_2=''

Each instance in RAC generates it's own archive files and has it's own redo log set.
The question is if all archive files are generated into a shared area (lets say NFS) can i use only one instance in RAC for redo shipping ?

Report message to a moderator

Previous Topic:	Physical Standby Failover Scenario
Next Topic:	Standby Database with 10g Standard Edtion

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Sat Feb 21 14:47:05 CST 2026