|
Hi!
Which version of DB?
Do you allow end users into database?
Maybe someone is doing massive DML?
Maybe your temporary tablespaces are dictionary managed and in logging
mode - some user has forgot few where clauses in SQL and is doing huge
sorting/joining?
You should check redo size statistic from v$session and find which one
generates the most redo.
If you are monitoring only the number of archives, then you should check
the size of them as well, for example in 9i you can have archive_lag_target
parameter which can do logswitches before logs are full, thus increasing the
number of archives, however the amount in bytes remains the same.
Tanel.
|
- Redo Logs Problem Munish Bajaj
- RE: Redo Logs Problem Hatzistavrou John
- RE: Redo Logs Problem Naveen Nahata
- RE: Redo Logs Problem Munish Bajaj
- RE: Redo Logs Problem Naveen Nahata
- RE: Redo Logs Problem Sarnowski, Chris
- RE: Redo Logs Problem Tanel Poder
- RE: Redo Logs Problem Whittle Jerome Contr NCI
- RE: Redo Logs Problem Smith, Ron L.
- RE: Redo Logs Problem Wiegand, Kurt
- RE: Redo Logs Problem Jeremiah Wilton
- RE: Redo Logs Problem Hately, Mike (LogicaCMG)
- RE: Redo Logs Problem Wiegand, Kurt
- Re: Redo Logs Problem AK
- Re: Redo Logs Problem M Rafiq
- Re: Redo Logs Problem Tanel Poder
- Re: Redo Logs Problem Jeremiah Wilton
