SWITCH_MVIEW_MASTER Procedure

This procedure changes the master site of a materialized view group to another master site. This procedure does a full refresh of the affected materialized views and regenerates the triggers and their associated packages as needed. This procedure does not push the queue to the old master site before changing master sites.

If generate_80_compatible is false for the materialized view and the new master site is a release lower than Oracle release 8.0, then regenerate replication support for the materialized view with generate_80_compatible set to true.

You can set both parameters for a materialized view in one call to DBMS_REPCAT.GENERATE_MVIEW_SUPPORT.

Note:

You cannot switch the master of materialized views that are based on other materialized views (level 2 and greater materialized views). Such a materialized view must be dropped and re-created if you want to base it on a different master.

See Also:

"GENERATE_MVIEW_SUPPORT Procedure"

Syntax

DBMS_REPCAT.SWITCH_MVIEW_MASTER (
   gname         IN   VARCHAR2, 
   master        IN   VARCHAR2,
   gowner        IN   VARCHAR2  := 'PUBLIC');

Parameters

Table 18-135 SWITCH_MVIEW_MASTER Procedure Parameters

Parameter	Description
gname	Name of the materialized view group for which you want to change the master site.
master	Fully qualified database name of the new master site to use for the materialized view group.
gowner	Owner of the materialized view group.

Exceptions

Table 18-136 SWITCH_MVIEW_MASTER Procedure Exceptions

Exception	Description
nonmview	Invocation site is not a materialized view site.
nonmaster	Specified database is not a master site.
commfailure	Specified database is not accessible.
missingrepgroup	Materialized view group does not exist.
qrytoolong	Materialized view definition query is greater 32 KB.
alreadymastered	At the local site, there is another materialized view group with the same group name mastered at the old master site.