VinodNagpure wrote:
But we were not cloning this instance, and the instance which was being cloned is ok. The database as well as the application is open. The issue is with another database running on the same server.

I suspect that the "working" DB has a file that over-wrote a file of the DB reporting the errors.

VinodNagpure wrote:
We don't have any backup as this is a test instance. Flashback too is not enabled ! Is clearing the logfiles and open resetlogs an option here ?

00338, 00000, "log %s of thread %s is more recent than control file"
// *Cause: The control file change sequence number in the log file is
// greater than the number in the control file. This implies that
// the wrong control file is being used. Note that repeatedly causing
// this error can make it stop happening without correcting the real
// problem. Every attempt to open the database will advance the
// control file change sequence number until it is great enough.
// *Action: Use the current control file or do backup control file recovery to
// make the control file current. Be sure to follow all restrictions
// on doing a backup control file recovery.

I am not clear if the controlfile or redo logfile got over written.
You would be wise to take a complete backup before trying any recovery action;
so you can at least get back to where you are now.

The datafiles are all there but looks like our redo log files are overwritten by wrong instance while doing restore and recover by rman. During cloning of another instance, this must have happened after controlfile is restored by rman and then at the time of renaming the redo logs.