hi,

I hv been trying to implement the above function using the example from oracle website as follow but i am not too sure

1) the 'orc1.world' is it the dblink name or the tnsname in the tnsnames.ora

2)assumming the prob in 1) is the dblink that was specifically connecting to a user...i then encountered problem at
DBMS_REPCAT.CREATE_MVIEW_REPGROUP stage where STMDDBLINK is my dblink name to a remote database ...these are the error

"ORA-06550: line 1, column 8:
PLS-00201: identifier 'SYS.DBMS_REPCAT_UTL2@STMDDBLINK' must be declared
ORA-06550: line 1, column 8:
PL/SQL: Statement ignored
ORA-06550: line 1, column 7:
PLS-00201: identifier 'SYS.DBMS_REPCAT_UNTRUSTED@STMDDBLINK' must be declared
ORA-06550: line 1, column 7:
PL/SQL: Statement ignored
ORA-06512: at "SYS.DBMS_REPCAT_UTL", line 2394
ORA-06512: at "SYS.DBMS_REPCAT_SNA_UTL", line 1699
ORA-06512: at "SYS.DBMS_REPCAT_SNA", line 64
ORA-06512: at "SYS.DBMS_REPCAT", line 1262
ORA-06512: at line 2"

3) Assumming it is the tnsnames in tnsnames.ora ...i encounter error at the same DBMS_REPCAT.CREATE_MVIEW_REPGROUP stage ...with the following errors where "Mview_grp" is the name i specified and i used a valid tnsname in my tnsnames.ora to point to a remote database...I wonder what have i missed out?any guru can enlighten??

"ORA-23313: object group "PUBLIC"."MVIEW_GRP" is not mastered at stmdgb
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 105
ORA-06512: at "SYS.DBMS_REPCAT_SNA_UTL", line 1690
ORA-06512: at "SYS.DBMS_REPCAT_SNA", line 64
ORA-06512: at "SYS.DBMS_REPCAT", line 1262
ORA-06512: at line 2"







=================================================================
Oracle website on creation of updateable materialized view
================================================================
Updatable Materialized Views
You can make a materialized view updatable during creation by including the FOR UPDATE clause or enabling the equivalent option in the Replication Management tool. For changes made to an updatable materialized view to be pushed back to the master during refresh, the updatable materialized view must belong to a materialized view group.

Updatable materialized views enable you to decrease the load on master sites because users can make changes to the data at the materialized view site. The following is an example of an updatable materialized view:

CREATE MATERIALIZED VIEW hr.departments FOR UPDATE AS
SELECT * FROM hr.departments@orc1.world;


The following statement creates a materialized view group:

BEGIN
DBMS_REPCAT.CREATE_MVIEW_REPGROUP (
gname => 'hr_repg',
master => 'orc1.world',
propagation_mode => 'ASYNCHRONOUS');
END;
/


The following statement adds the hr.departments materialized view to the materialized view group, making the materialized view updatable:

BEGIN
DBMS_REPCAT.CREATE_MVIEW_REPOBJECT (
gname => 'hr_repg',
sname => 'hr',
oname => 'departments',
type => 'SNAPSHOT',
min_communication => TRUE);
END;

/
================================================================