Is there a max number of mins for DELAY parameter? [message #353404] |
Mon, 13 October 2008 14:18 |
todis
Messages: 8 Registered: January 2008
|
Junior Member |
|
|
We are running 10gr2 and we currently have scripts set up to switch our two standby's from read only/recover mode. We now need to change one standby to be in recover mode all the time but delay the application of the logs. I plan on using the DELAY parameter:
SQL> ALTER SYSTEM SET LOG_ARCHIVE_DEST_2='SERVICE=stdby_srvc DELAY=60';
My question is if there is a max value for this parameter. All the notes I read talk about 30mins, four hours, etc. My manager wants it set to 72 hours. Will this work or is the delay too long? The manual states the following:
"The time interval
(expressed in minutes) starts when the archived redo log files are successfully archived
at the standby site."
I'm wondering if 72 hours is too long and I'm kind of unclear as to how the time interval works. Does the "timer" reset itself every time a new log file is successfully transferred? If so will the standby ever apply the logs if it is receiving them on a consistent basis and it's delayed 72 hours? Has anyone used a delay setting this high?
we're on 10.2.0.4 on Solaris 10u5, SPARC
Thanks in advance.
[Updated on: Mon, 13 October 2008 14:21] Report message to a moderator
|
|
|
|
|
|
|
|