Archivelog Duplexing

[former_member759680]

Hello,

We have implemented duplexing of archivelogs.

So now we have 2 copies of every archivelog on the server

/oraarch and /oraarch_duplex

The files from /oraarch_duplex are moved by a script to the DR server. While BRARCHIVE deletes the backed up archivelogs from /oraarch.

What woudl ahppen if /oraarch_duplex is 100% full but there is free space in /oraarch?

Would the database come to a standstill?

Regards,

Gautam.

[Former Member · Accepted solution]

Hi Guatam,

>> What woudl ahppen if /oraarch_duplex is 100% full but there is free space in /oraarch?

The database will not be hang, because of the LOG_ARCHIVE_MIN_SUCCEED_DEST default value is 1.

Check the link http://download.oracle.com/docs/cd/A97630_01/server.920/a96521/archredo.htm

Best regards,

Orkun Gedik

[former_member524429]

Hi,

As per this [SAP Note 797315|https://service.sap.com/sap/support/notes/797315], you can set oracle parameter [archive_dupl_del = only|http://help.sap.com/SAPHELP_NWPI71/helpdata/EN/47/347c7a6c4b1a52e10000000a1553f7/frameset.htm] to fulfill your requirement.

But, you can take the benefit of recommended oracle parameter log_archive_dest_2 which can be directly pointed to your DR site oraarch location with entry like log_archive_dest_2=service=<SID>.dest2 optional reopen=180. The <SID>.dest2 should be maintained in tnsnames.ora file of your Primary site & DR Site as followed.

<SID>.dest2=

(DESCRIPTION =

(ADDRESS_LIST =

(ADDRESS =

(COMMUNITY = SAP.WORLD)

(PROTOCOL = TCP)

(HOST = <DR_hostname>)

(PORT = 1527)

)

)

(CONNECT_DATA =

(SID = <SID>)

(GLOBAL_NAME = <SID>.dest2)

)

)

The above mentioned strategy is used in Roll Over DR Site.

Regards,

Bhavik G. Shroff

Edited by: Bhavik G. Shroff on Aug 17, 2011 4:37 PM