Skip to Main Content

Oracle Database Discussions

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Inappropriate max(sequence#) after database restore/recovery

Abhijit GourAug 29 2016 — edited Aug 31 2016

Hi All,

I've seen difference in log file sequence as below - recently we've restored this database from full DB RMAN backup, major thing that we still see is max(sequence#) old value as before restore and before DB was opened with resetlog.

What can cause this difference in max(sequence#)? Is there any solution to bring it on sync appropriately?

Please advise.

SQL> archive log list

Database log mode              Archive Mode

Automatic archival             Enabled

Archive destination            /oralogs/RMXPROD/arch01

Oldest online log sequence     688

Next log sequence to archive   695

Current log sequence           695

SQL>

SQL> select max(sequence#) from v$archived_log;

MAX(SEQUENCE#)

--------------

         13303

Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Sep 28 2016
Added on Aug 29 2016
9 comments
2,375 views