High Availability Data Guard, Sharding and Global Data Services (MOSC)

MOSC Banner

Data mismatch between standby DB instances

in High Availability Data Guard, Sharding and Global Data Services (MOSC) 1 commentAnswered

Hi All

I believe this is well-known issue or even intended behavior..

Background : We have standby DB in "read only with apply" mode in RAC environment (Linux x86-64 Oracle 12.1). Standby is running and synchronizing with primary, sometime short lags take place because of MaxPerformance mode but in general standby is in sync.

Issue : Eventually after some DDL like truncate or drop partition users reported data mismatch between primary and standby DB. Meantime standby was in sync with primary ! Short investigation found actual data when i retrieve them from one instance of standby db and "old" data or even "ORA-08103: object no longer exists" for another instance of the same standby DB. Actual data retrieve from instance with MRP process or apply instance. I explicitly assign apply instance and DB service on the same node as workaround but

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center