[Oracle-l] [Replication] Altering Master Object at materialized view replication environment

Dennis,

That's one of the nuances of MV replication. If you alter the master table,
you have to drop and recreate the MV on the snapshot site. This is as per
Oracle's internal documentation.

However, there is a trick. If you have created the MV using a prebuilt
table, then you can have a workaround. When you build an MV on a table,
Oracle simply assumes the type of the segment as MV rather than the table,
i.e. the segment that used to be known as the table is now known as the MV.
when the MV is dropped, Oracle does not drop the segment; rather it reverts
the type to the table as it used to be.

So when you alter the master table, follow the sequence of steps.

stop replication
drop the MV
alter the master table
alter the prebuilt table in the same way.
Build the MV on the prebuilt table again.

Of course, there are several small but crucial steps to be followed. I have
described the procedure completely in http://www.dbazine.com/nanda2.html .

Hope this helps.

Arup Nanda

Original Message -----
To: "Multiple recipients of list ORACLE-L"
Sent: Tuesday, January 14, 2003 3:53 AM
replication environment

Hello!
per Oracle's internal documentation.

:-(
Thank you, it works.
But it's reasonable only if a table size is huge ... or channel capacity
is small :-), so complete refresh becoms very expensive operation ...

/sds

PS: About " http://www.dbazine.com/nanda2.html ", imho, something wrong
in this sentence:
"The table has two columns, COL1 NUMBER (9) and COL2 CHAR(1000), COL3
CHAR(900)" ... 8-)

Dennis,

I am glad that it worked for you. Of course, it's useful if the table size
is big. In case of a small table, you would just drop and recreate the
snapshot.

Thanks for pointing out the typo.

Regards,

Arup

Original Message -----
To: "Multiple recipients of list ORACLE-L"
Sent: Monday, January 20, 2003 9:44 AM
replication environment