why Lots of Archive Logs file generating even not working the database

why Lots of Archive Logs file generating even not working the database

checklists :-

1) Sometimes Parallel Rollback of Large Transaction may become very slow. After
killing a large running transaction (either by killing the shadow process or
aborting the database) then database seems to hang, or smon and parallel query
servers taking all the available cpu. After killing shadow process or aborting
the database the v$transaction entry is lost, so you cannot estimate by
examining v$transaction.used_ublk how the rollback procedure proceeds.

solution:-

If you fall into the above case you can use

alter system set fast_start_parallel_rollback = false;

in order to disable parallel rollback.

If it hangs, shutdown database and define it inside init.ora file:

fast_start_parallel_rollback = false


2) Make the changes to your database by setting temp tablespace type to TEMPORARY
and setting the temp tablespace to the nologging option.


3) Make sure any submitted and/or scheduled jobs are running in OS level and database level.If so, disable the jobs.


You can also check your redo log file or archive log file using log miner utility.
using log miner you can see the redo entry/transaction. then will be sure what are cause of generating so many archive log or redo log.
for this see here...
http://halimdba.blogspot.com/2010/08/using-logminer-to-analyze-redo-log.html