Most probably you did a shutdown abort in order to speed up the bounce process 🙂 so you can set your database into archivelog mode.Below, you can find an example of how one can reproduce this error: The solution is an easy one. All you have to do is to bring you database in OPEN…
Below you can find one of the available solutions that can be applied to solve this issue: PRI select max(sequence#) from v$archived_log where applied=’YES’; STBY select max(sequence#) from v$archived_log where applied=’YES’; SQL> select * from v$archive_gap; Â Â THREAD# LOW_SEQUENCE# HIGH_SEQUENCE# ———- ————- ————– Â Â Â Â Â Â Â Â 1Â Â Â Â Â Â Â Â Â 285Â Â Â Â Â Â Â Â Â Â 285 RMAN> list ARCHIVELOG FROM SEQUENCE 286 until SEQUENCE…
