Hi all,
My first question - Is it possible to have an Updatable Materialized
View and the associated Master Table located on the same database?

This is the requirement scenario:
One unique database D exists.
A is a batch table. Only inserts are allowed on Table A.
M is an updatable materialized view on Table A (Master). Only updates
are allowed on M (no insert or delete).
Requirement is to push updates/changes from M to A periodically and
then get the new inserted records from A into M via a refresh.

Is this possible? What other approaches are applicable here?

cheeky wrote:
> Hi all,
> My first question - Is it possible to have an Updatable Materialized
> View and the associated Master Table located on the same database?

Yes.
--
Daniel A. Morgan
University of Washington
damorgan@x.washington.edu
(replace x with u to respond)
Puget Sound Oracle Users Group
www.psoug.org

DA Morgan wrote:
> Yes.
> --
> Daniel A. Morgan

Do I need to create Master Group and Materialized View Group to attain
this?

Thanks for your response(s)!

My question is related to the implementation and setup of the
environment as explained in the above example. How can I achieve this
considering that I have created an updatable m-view?

If possible, how do I push changes made to an updatable m-view back to
it's master table when/before I execute DBMS_MVIEW.REFRESH on the
m-view? What is the procedure to do this if both table and mview exist
on the same database? Do I need to create master groups, materialized
view refresh groups, etc.?

One more thing.. Is there a way to retain changes to the m-view during
refresh? In this case, only newly inserted/updated records in the
associated table would get inserted into m-view. Whereas changes made
to m-view records would stay as-is.

Hope my question is directed well. Thanks for your help.