Skip to Main Content
  • Questions
  • Sequence no mismatch between Primary and Standby

Breadcrumb

Question and Answer

Connor McDonald

Thanks for the question, vinod.

Asked: February 12, 2018 - 9:03 am UTC

Last updated: February 14, 2018 - 1:43 am UTC

Version: 11g

Viewed 1000+ times

You Asked

Hi,

I have taken backup from primary database that time the max sequence number was 285 which was applied on standby. after few minutes had an issue in standby database so that i dropped standby database permanently. so here what i done..restored primary latest backup in standby and started the MRP Process..so here whatever changes are happening in Primary DB the same time which reflects on standby database and observed archivelogs also transferring properly in respective locations.

My Question is....

The primary DB is showing still max(sequence#) is 285 but standby shows max(sequence#) is 15...Even after made so many changes also still the primary showing 285..why the Sequence not matching.




and Connor said...

Take a look here

https://connor-mcdonald.com/2016/07/08/can-a-query-on-the-standby-update-the-primary/

Sequences between primary and standby are handled slightly differently

Rating

  (1 rating)

Is this answer out of date? If it is, please let us know via a Comment

Comments

Topic Diverted to different conecept

VINOD KUMAR KORADA, February 13, 2018 - 3:58 pm UTC

Here am asking about Data guard Replication.
Connor McDonald
February 14, 2018 - 1:43 am UTC

My mistake...but since you just said:

"max sequence number was 285"

you can reasonably expect that we assume you are talking about sequences.

If you said something like:

"I queried V$LOG_HISTORY like this

select max(sequence#)
from V$LOG_HISTORY"


then maybe we could have benefitted from the extra *precision* in your question.

For standby lag, check the alert log on each database.

More to Explore

Administration

Need more information on Administration? Check out the Administrators guide for the Oracle Database