Database DataWarehousing (MOSC)

MOSC Banner

materialized view and archive logs

edited Nov 8, 2011 2:10AM in Database DataWarehousing (MOSC) 3 commentsAnswered
Is there a way to prevent writing archive log on a materialized view that is refreshed complete (i.e., not Fast?) without using "atomic_refresh=>FALSE" ?  We cannot risk the materialized view table being empty for the several seconds it takes to complete the full refresh, which is why we are unable to use "atomic_refresh=>FALSE" .  The materialized view has been created using "NOLOGGING", which appears to have had no affect on the creation of archive logs.

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