V$LOG is your friend. There are two interesting columns to you: - one reflects that there redo log needs to be archived (than ARC performace is bad). - another one reflects that redo log is required for crash recovery - and you need to look at DBWR performance and your checkpointing.
I'm having a big problem my database is stopping for like 20 seconds because it can not write to it redo log
As it looks it seems to be full, but this should not be. The acriver is archiving group 3 and the lgwr wants to write to group 1. Is there anyone how has had this problem before. Or who might have some tips on where or how i can solve this.
I have looked for I/o problme but this does not seen to be the problem
-- Vincent Verpoort
,.-~`"'~-.,_,.-~`"'~-.,_,.-~`"'~-.,_,.-~`"'~-.,_,.-~`"'~-.,_ Communiceren is begrepen worden ^*<-._,.->*^*<-._,.->*^*<-._,.->*^*<-._,.->*^*<-._,.->*^*<-.
-- Best regards, Alex Gorbachev
http://blog.oracloid.com -- //www.freelists.org/webpage/oracle-l