Attention: To align with new corporate security policies, and to match policies adopted by other communities within Oracle, the My Oracle Support Community access requirements will change beginning September 18, 2025. MOSC will now require that member accounts in our community be associated to a *corporate* email address. This means that users with generic domains (such as gmail.com, yahoo.com, and others) will no longer be granted access to the discussion forums and ideas labs. If this policy affects you, act now to change the email address that is associated with your Oracle (and community) account. Alternatively, you can opt to create a new Oracle account that uses your corporate email domain.

Database DataWarehousing (MOSC)

Materilized View Dropping vs.Truncating.

Sep 3, 2009 4:15AM edited Jan 14, 2010 1:19AM in Database DataWarehousing (MOSC) 8 commentsAnswered ✓

I have a script that drops a materialized view then creates the view. I've notice that the lots of logging

occurs during this job. To reduce the amount of logging, I have added the NOLOGGING clause to the

creation of the materialized view. So I started to think, what is better:

A) Drop the materialized view (without a purge) the create the table or...
Truncate the materialized view then insert to the materialized view.

What is the least contentious operation? What operations would cause the least about of log switching?

Thanks.

0

Howdy, Stranger!

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

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

Category Leaderboard

Top contributors this month