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

MOSC Banner

Remediation for Use of NOLOGGING in Database with a Standby

edited Nov 6, 2013 7:58AM in High Availability Data Guard, Sharding and Global Data Services (MOSC) 7 commentsAnswered
 I have a very large 11gR2 database. It has a mixed workload of batch processing, data loading, batch calculation, reporting and some transactional work.  The application does write large amounts of data that are not kept, so when the database was implemented 4 years ago and a DG standby was created, the databases were not set to FORCE LOGGING.  Unfortunately the application developers have used NOLOGGING in other places where they did want data kept.  This does invalidate our standby.  Where we need to keep the data on failover to a standby, I will be changing any such tables to

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