Hi Alessandro, Your scenario looks pretty much allright. In fact you can skip teh DEFER/ENABLE part of LOG_ARCHIVE_DEST_2. If you just set the whole parameter, it will take effect upon the next log switch. Don't forget to set (if not set already): - STANDBY_ARCHIVE_DEST at the standby - LOG_ARCHIVE_CONFIG at both - FAL_CLIENT/FAL_SERVER at the standby - eventually ARCHIVE_LAG_TARGET at the primary include PARALLEL in the LOG_ARCHIVE_DEST_2 parameter (or specify ASYNC) Consider a DELAY for applying archive logs, to enable you to overcome human/logical errors Also dig into the NET_TIME_OUT, MAX_FAILURE and other 'network connection' related parameters. Best regards, Carel-Jan Engel === If you think education is expensive, try ignorance. (Derek Bok) === On Fri, 2006-12-01 at 15:51 +0100, Alessandro Vercelli wrote: > Hi everybody, > in have a physical standby DG configuration with 2 nodes: > - Oracle sever 10.1.0.5 on RHEL ES 3 > - reserved internal LAN for Log Transport with dedicated listener > - ARCn is used for redo data archiving, maximum performance mode > > In order to enable SRLs, I would like to change ARCn to LGWR for redo data > archiving, with the following steps: > > - stop recover process on standby (shutdown and mount ?) > - create the standby logfiles on standby > - LOG_ARCHIVE_DEST_STATE_2=DEFER on primary > - modify LOG_ARCHIVE_DEST_2 on primary (on stanndby too for primary role) > - create the standby logfiles on primary > - start recover process on standby (alter database recover managed...) > - LOG_ARCHIVE_DEST_STATE_2=ENABLE > > Am I missing something, or hints/caveats to pay attention? > > Thanks for your help, > > Alessandro > > > > ------------------------------------------------------ > Passa a Infostrada. ADSL e Telefono senza limiti e senza canone Telecom > http://click.libero.it/infostrada01dic06 > > > -- > //www.freelists.org/webpage/oracle-l > >