Thanks a lot to all who replied !
DBAndrey
* 03-9254520
* 058-548133
* mailto:[EMAIL PROTECTED]
-Original Message-
Sent: Sunday, August 18, 2002 6:36 PM
To: LazyDBA.com Discussion; Andrey Bronfin
After researching lot of issues with having smaller size
redo logs , we opted for so
No, but this is close...
"ARCHIVE_LAG_TARGET
ARCHIVE_LAG_TARGET limits the amount of data that can
be lost and effectively increases the availability of
the standby database by forcing a log switch after a
user-specified time period elapses.
A 0 value disables the time-based thread advance
feat
Oracle9i hasn't introduced such a parameter; the best way to achieve what
you want below 9i is to resize redo logs to be smaller (which several
replies have already mentioned)...
With 9i Data Guard, you have options where you can set LGWR to ship redo log
files to the standby, and there is even
I am not sure if 9i has introduced any such parameter.
Other than sizing smaller redo log files [but that still doesn't guarantee
that you get a log-switch every X minutes], you'd have to write
a DBMS_JOB or a CRON job to do an ALTER SYSTEM SWITCH LOGFILE.
Hemant
At 06:08 AM 18-08-02 -0800, you
Andrey, I assume, version < 9.x of the database?(if i'm wrong let me
know and we can talk about 9i features of data guard).
How about a job(via dbms_job) to do what you want?
joe
Andrey Bronfin wrote:
>Dear gurus !
>It's either a Sunday's dead brain or ..
>Is there an init.ora parameter
Ron , thanks a lot !
I know this solution , but:
there are certain pick-times when there are many activities going on against
the DB. Therefore making the redo logs smaller will cause performance
problems. So , i'd have this solution as a last resort, in case i will not
find an init.ora solution.
Dear gurus !
It's either a Sunday's dead brain or ..
Is there an init.ora parameter to force redo logs switch every 3 minutes or
so ?
( the reason is that I need frequent log switches in order for the standby
database to pickup changes frequently , i.e. to be "almost" in sync with the
primary