ORA-00338: log # of thread # is more recent than control file
It could be that you are opening using the wrong control file[s]. This is easily caused when using for example a parameter file in ASM - the correct one - and one in the default location $ORACLE_HOME/dbs/ that still has the old references in place after a migration to ASM. In that case search in ASM to the current control files.

In such a setup, normally the parameter is found by using srvctl config database -d YOUR_DB

During every opening attempt the log# is increased .... so after many attempts, the error can go away and the problem can still exist ....