Пересоздание REDO LOG INACTIVE ORA-00312 : Oracle

OlegON ➤ В алерте какие строки +-10 строк от ошибки?

PMON started with pid=2, OS id=1996
PSP0 started with pid=4, OS id=3720
MMAN started with pid=6, OS id=2768
DBW0 started with pid=8, OS id=2312
DBW1 started with pid=10, OS id=3892
LGWR started with pid=12, OS id=3436
CKPT started with pid=14, OS id=1684
SMON started with pid=16, OS id=3176
RECO started with pid=18, OS id=3340
CJQ0 started with pid=20, OS id=796
MMON started with pid=22, OS id=3480
MMNL started with pid=24, OS id=416
Wed Dec 04 16:00:41 2013
alter database mount exclusive
Wed Dec 04 16:00:45 2013
Setting recovery target incarnation to 1
Wed Dec 04 16:00:45 2013
Successful mount of redo thread 1, with mount id 221983081
Wed Dec 04 16:00:45 2013
Database mounted in Exclusive Mode
Completed: alter database mount exclusive
Wed Dec 04 16:00:45 2013
alter database open
Wed Dec 04 16:00:45 2013
Errors in file d:\oracle\admin\kamavto\bdump\kamavto_lgwr_3436.trc:
ORA-00314: log 2 of thread 1, expected sequence# 35255 doesn't match 35258
ORA-00312: online log 2 thread 1: 'D:\ORACLE\ORADATA\KAMAVTO\REDO02.LOG'

Wed Dec 04 16:00:45 2013
Errors in file d:\oracle\admin\kamavto\bdump\kamavto_lgwr_3436.trc:
ORA-00314: log 2 of thread 1, expected sequence# 35255 doesn't match 35258
ORA-00312: online log 2 thread 1: 'D:\ORACLE\ORADATA\KAMAVTO\REDO02.LOG'

ORA-314 signalled during: alter database open...

OlegON ➤ ORA-00314 у тебя ошибка... если open resetlogs не работает и _allow_resetlogs_corruption, а это, скорее всего, так и будет, то медленно и печально играй что-то подобающее и читай, сколько раз про архивлог тут было сказано...

OlegON ➤ и читай, сколько раз про архивлог тут было сказано...