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

MOSC Banner

Logical Data Guard: After nologging insert in primary database, SQL Apply stops in standby db with O

edited Dec 10, 2012 5:50AM in High Availability Data Guard, Sharding and Global Data Services (MOSC) 13 commentsAnswered
Hello experts,

I have a doubt regarding SQL Apply behaviour after nologging operations in primary database.

We have a 10.2.0.5 Data Guard (DG): 1 primary database + 1 standby database. The DG is a logical one. Standby database is used just for reporting, not for DR. So no switchover or failover will ever happen.

Applications occasionally need to perform some NOLOGGING operations in primary database for massive data upload. I know it is not recommended but they really need it because of the amount of data.

We have conducted some tests and every time a NOLOGGING operation is performed in primary db, SQL Apply stops in standby with next error:

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