Are your redo logs and Archive logs on the same disk? If so move them to seperate disks.
I think the parameter log_archive_max_processes can be used to define more Arch processes (but I would check this beofre setting it).
If your on Unix you can see how many arch processes are running by entering the following at the command line...
ps -ef |grep arc
These are information messages and as long as they're followed by a 'Completed Archiving' message for that log file should be OK. Look at ways of tuning the Arc process. (you could try http://www.ixora.com.au/tips/tuning/archiver.htm for info)
Since you have 3 loggruops you don't need to add any more.(well you can always ) but i don't think that's necessary.
Destination of arch files.
try to reduce the time of redo log switching by increasing the size of redo logfiles, on a default db creation it's 1mb each ,make it 10mb each or so.
you don't need to create any aditional arc processes as the lgwr automatically starts one if necesary but you can do it if you want to.
I'm a JOLE(JavaOracleLinuxEnthusiast)
--- Everything was meant to be---
Originally posted by TomazZ I don't know.
Probably ARC1 doesn't know that ARC0 is doing this log until it's finished, and just tries.
But it looks stupid...
Everything I found on metalink was explanation, that one is manually issued with 'alter system archive log current'.
But in my case it wasn't it. Nor in yours, i guess.
I can't really remember now, if restarting just archiver helps, or database should be rebounced. Try.
look at asktom.oracle.com, and you will know the answer, i post his words here: not his original words:
Just as tomazz said, one archiver process doesnot know the others is process(archiving) this log file, so there is error message like that, in fact, this is just a harmless warning, in 9i , it is improved.