Error while creating MV replication group object

Question

Hi,
I am getting error while creating replication group object. I tried to create using OEM and SQLPlus
OEM error
This error while creating M.V. rep. group object
There is a table or view named SCOTT.EMP.
It must be dropped before a materialized view can be created.
In SQLPLUS
SQL> CONNECT MVIEWADMIN/MVIEWADMIN@SWEET
Connected.
SQL>
SQL> BEGIN
2 DBMS_REPCAT.CREATE_MVIEW_REPOBJECT (
3 gname => 'SCOTT',
4 sname => 'KARTHIK',
5 oname => 'emp_mv',
6 type => 'SNAPSHOT',
7 min_communication => TRUE);
8 END;
9 /
BEGIN
ERROR at line 1:
ORA-23306: schema KARTHIK does not exist
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 86
ORA-06512: at "SYS.DBMS_REPCAT_SNA_UTL", line 2840
ORA-06512: at "SYS.DBMS_REPCAT_SNA_UTL", line 773
ORA-06512: at "SYS.DBMS_REPCAT_SNA_UTL", line 5570
ORA-06512: at "SYS.DBMS_REPCAT_SNA", line 82
ORA-06512: at "SYS.DBMS_REPCAT", line 1332
ORA-06512: at line 2
Please not already I have created KARTHIK schema.

Answer 1

Arthik,
I think I know what may have happened.
As I can see you are trying to create support for an updateable materialized view.
You have to make sure the name of the schema that owns the materialized view is the same as the schema owner of the master table (at master site).
From the code you have shown, I bet the owner of table EMP is SCOTT.
From the other hand, you want to create materialized view EMP_MV under schema KARTHIK that refers to table SCOTT.EMP at master site.
According to the documentation, the schema name used in DBMS_REPCAT.CREATE_MVIEW_REPOBJECT must be same as the schema that owns the master table.
Please check the documentation at the link below
http://download.oracle.com/docs/cd/B19306_01/server.102/b14227/rarrcatpac.htm#i109228
I tried to reproduce your example in my environment, and I got exactly the same error which actually confirms my assumption that the reason for the error is the fact that you tried to create the materialized view in a schema with different name than the one where master table exists.
I'll skip some of the steps that I used to create the replication environment.
I have two databases, DB1.world and DB2.world
On DB2.world I will generate replication support for table EMP which belongs to user SCOTT
SQL> conn scott/*****@DB2.world
Connected.
SQL>create materialized view log on EMP with primary key;
Materialized view log created.
SQL>
SQL>conn repadmin/*****@DB2.world
Connected.
SQL>BEGIN
  2       DBMS_REPCAT.CREATE_MASTER_REPGROUP(
  3         gname => 'GROUPA',
  4         qualifier => '',
  5         group_comment => '');
  6*   END;
PL/SQL procedure successfully completed.
SQL>BEGIN
  2       DBMS_REPCAT.CREATE_MASTER_REPOBJECT(
  3         gname => 'GROUPA',
  4         type => 'TABLE',
  5         oname => 'EMP',
  6         sname => 'SCOTT',
  7         copy_rows => TRUE,
  8         use_existing_object => TRUE);
  9*   END;
10  /
PL/SQL procedure successfully completed.
SQL> BEGIN
  2       DBMS_REPCAT.GENERATE_REPLICATION_SUPPORT(
  3         sname => 'SCOTT',
  4         oname => 'EMP',
  5         type => 'TABLE',
  6         min_communication => TRUE);
  7    END;
  8  /
PL/SQL procedure successfully completed.
SQL>execute DBMS_REPCAT.RESUME_MASTER_ACTIVITY(gname => 'GROUPA');
PL/SQL procedure successfully completed.
SQL> select status from dba_repgroup;
STATUS                                                                         
NORMAL                                                                          Now let's create updateable materialized view at DB1. Before that I want to let you know that I created one sample in DB1 user named MYUSER. MVIEWADMIN is Materialized View administrator.
SQL>conn mviewadmin/****@DB1.world
Connected.
SQL>   BEGIN
  2       DBMS_REFRESH.MAKE(
  3         name => 'MVIEWADMIN.MV_REFRESH_GROUPA',
  4         list => '',
  5         next_date => SYSDATE,
  6         interval => '/*1:Hr*/ sysdate + 1/24',
  7         push_deferred_rpc => TRUE,
  8         refresh_after_errors => TRUE,
  9         parallelism => 1);
10    END;
11  /
PL/SQL procedure successfully completed.
SQL>   BEGIN
  3       DBMS_REPCAT.CREATE_SNAPSHOT_REPGROUP(
  5         gname => 'GROUPA',
  7         master => 'DB2.wolrd',
  9         propagation_mode => 'ASYNCHRONOUS');
11    END;
12  /
PL/SQL procedure successfully completed.
SQL>conn myuser/*****@DB1.world
Connected.
SQL>CREATE MATERIALIZED VIEW MYUSER.EMP_MV
  2    REFRESH FAST
  3    FOR UPDATE
  4    AS SELECT EMPNO, ENAME, JOB, MGR, SAL, COMM, DEPTNO, HIREDATE
  5*      FROM   [email protected];
Materialized view created.
SQL>conn mviewadmin/******@DB1.world
Connected.
SQL> BEGIN
  2       DBMS_REFRESH.ADD(
  3         name => 'MVIEWADMIN.MV_REFRESH_GROUPA',
  4         list => 'MYUSER.EMP_MV',
  5         lax => TRUE);
  6    END;
  7  /
PL/SQL procedure successfully completed.And now lets run CREATE_MVIEW_REPOBJECT.
SQL>   BEGIN
  2       DBMS_REPCAT.CREATE_MVIEW_REPOBJECT(
  3         gname => 'GROUPA',
  4         sname => 'MYUSER',
  5         oname => 'EMP_MV',
  6         type => 'SNAPSHOT',
  7         min_communication => TRUE);
  8    END;
  9  /
  BEGIN
ERROR at line 1:
ORA-23306: schema MYUSER does not exist
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 86
ORA-06512: at "SYS.DBMS_REPCAT_SNA_UTL", line 2840
ORA-06512: at "SYS.DBMS_REPCAT_SNA_UTL", line 773
ORA-06512: at "SYS.DBMS_REPCAT_SNA_UTL", line 5570
ORA-06512: at "SYS.DBMS_REPCAT_SNA", line 82
ORA-06512: at "SYS.DBMS_REPCAT", line 1332
ORA-06512: at line 3 I reproduced exactly the same error message.
So the problem is clearly in the schema name that owns the materialized view.
Now lets see if what would happen if I create the MV under schema SCOTT which has the same name as the schema on DB2.world where the master table exists.
SQL>conn scott/****@DB1.world
Connected.
SQL>CREATE MATERIALIZED VIEW SCOTT.EMP_MV
  2    REFRESH FAST
  3    FOR UPDATE
  4    AS SELECT EMPNO, ENAME, JOB, MGR, SAL, COMM, DEPTNO, HIREDATE
  5*      FROM   [email protected];
Materialized view created.
SQL>conn mviewadmin/******@DB1.world
Connected.
SQL> BEGIN
  2       DBMS_REFRESH.ADD(
  3         name => 'MVIEWADMIN.MV_REFRESH_GROUPA',
  4         list => 'SCOTT.EMP_MV',
  5         lax => TRUE);
  6    END;
  7  /
PL/SQL procedure successfully completed.And now lets run CREATE_MVIEW_REPOBJECT.
SQL>   BEGIN
  2       DBMS_REPCAT.CREATE_MVIEW_REPOBJECT(
  3         gname => 'GROUPA',
  4         sname => 'SCOTT',
  5         oname => 'EMP_MV',
  6         type => 'SNAPSHOT',
  7         min_communication => TRUE);
  8    END;
PL/SQL procedure successfully completed.As you can see everything works fine when the name of the schema owner of the MV at DB1.world is the same as the schema owner of the master table at DB2.world .
-- Mihajlo
Message was edited by:
tekicora