Skip to Main Content

Breadcrumb

May 4th

Question and Answer

Connor McDonald

Thanks for the question, Danish.

Asked: August 03, 2017 - 11:50 am UTC

Last updated: August 03, 2017 - 12:59 pm UTC

Version: 10.1.2

Viewed 1000+ times

You Asked

Is it possible to restrict creation of duplicate record in MLOG.

In our scenario, same record is updated twice then it is creating two record in MLOG and fast refresh is taking longer time.

Is it possible if it create only one record in MLOG not duplicate. so that next fast refresh will only do one delete/insert. Right now it is doing same task twice because two same records are in mlog.

and Connor said...

Nope.

Think about the complexity that this would entail in a multi user environment, where the "same" row in a base table could be updated, deleted-then-reinserted, updated later, etc etc. Plus the serialisation that you'd probably need to manage it all.

It's just not practical given the one the premises of materialized view logs in the first place is keep impact on the base table low and defer the effort of populating a summary table (the mview) in an asynchronous fashion.

Is this answer out of date? If it is, please let us know via a Comment

More to Explore

Design

New to good database design? Check out Chris Saxon's full fundamentals class.