HELP!! Urgent

Database giving error
alter database open
*
ORA-00322: log 9 of thread 1 is not current copy
ORA-00312: online log 9 thread 1: '/oracle/newspace/oradata/EPRO/log9.ora'

What to Do ?

Solution: RECOVER LOSS OF ONLINE REDO LOG


First check that ORACLE_HOME and ORACLE_SID are set correctly, and if not, do
so and re-start. Else, continue as follows.

Recover the loss of an inactive, online redo log group.

ALTER DATABASE CLEAR LOGFILE 'filename';

If there is more than one LOGFILE in the redo log group then you must
specify all the log files.

For example, the following fails:

SVRMGR> alter database clear logfile '/vobs/oracle/dbs/log3.log';
alter database clear logfile '/vobs/oracle/dbs/log3.log'
*
ORA-1514: error in log specification: no such log
ORA-1517: log member: '/vobs/oracle/dbs/log3.log

But, specifying all the log files in the group works:
SVRMGR> ALTER DATABASE CLEAR LOGFILE ('/vobs/oracle/dbs/t4.log','/vobs/oracle/;
Statement processed.

For more information Ref: Bug:763186


Solution Explanation:
=====================

The database, at open, does a check of log file headers and
found an online log that appears to be an incorrected restored file.
In this case it was not incorrect, but inactive. By issuing
the clear logfile, you can avoid going through an uneccessary
open resetlogs when applicable

Thanx a lot.
I did a little headstorming myself and had arrived at the same solution.
Thanx a lot again.

So which has preference or best of doing it. After recovery, to open with rest logs or clear the logs and archive 'em ??

WIll the SCN be in sync if we use Clear the logs option ?

Well, In my case I move the redo log file to a new location and when opening the database I got the error. When I tried to rest the logs It gave a error that rest logs is possible only after database recovery. So the only option left for me was to clear the logfile. Another option is to drop the logfile and recreate it.
thanx