I have an interesting issue. One of my prod database archive log frequency had reduced from 2Hrs to 3 min step by step avg since nov. Redo size is 100MB. I am sure my database is not that much hot. I observed the amount of changed blocks for 1hr (as per a metalink doc). It totals to around 50MB only. No direct load etc. Any guesses whatz going into redo log? My last attempt is about to explore log using Logminer. Before going into that, what are the likely causes?
No new index created/rebuilded since nov.
Abhaysk, Thanks for the support. Finally i got the hint from dba_waiters joining v$session and v$sql. It was series of update query updating same table, which was blocking all the sessions in application flow. It has been re-written and now the redo generation back to normal. 3 Hrs/switch average. Logminer too shown the same statement which helped me to narrow down to the issue.