One archive log every minute

Hello,

Can someone give me a hint on how to reduce the speed of generating archived redo logs (that is how to reduce speed of redo log switching).

By now our database switches once in 2-4 minutes when there is NO activity on it except several jobs. All that jobs do is scan several tables with a cursor to find certain records (which are surely not found when db is inactive).

I assume there is little or no internal activity (with commit/rollbacks) performed by DBMS_JOB and DBMS_ALERT.

Then why it keeps logging something? Is there any way to see the meaning of archive log's content?

Any hint or advise or doc ref will be helpful, thanks.

PS. BTW, if i increase the number of SNP processes, archiving frequency increases also, and vice versa.

Regards,
Igor

--
Igor Sereda,
ITC, Russia Received on Sun May 24 1998 - 11:45:35 CDT