ORA-23308 object does not exist or is invalid when DBMS_REPCAT.DROP_MASTER_

Question

HI,
I am working on oracle 10g multimaster replication.
When i try to drop object from master site it gives me error like
SQL> BEGIN
  2     DBMS_REPCAT.DROP_MASTER_REPOBJECT(
  3       oname => '"AC_CHECK"',
  4        type => 'TABLE',
  5       sname => '"UMESH"',
  6       drop_objects => FALSE);
  7  END;
  8  /
BEGIN
ERROR at line 1:
ORA-23308: object UMESH.AC_CHECK does not exist or is invalid
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.DBMS_REPCAT_UTL", line 2874
ORA-06512: at "SYS.DBMS_REPCAT_UTL", line 2849
ORA-06512: at "SYS.DBMS_REPCAT_UTL4", line 2926
ORA-06512: at "SYS.DBMS_REPCAT_UTL4", line 2727
ORA-06512: at "SYS.DBMS_REPCAT", line 643
ORA-06512: at line 2I can't find out the reason for it.
I more problum i am facing is when i stopped ( quiesced ) the replication activity.
my stored procedures on the master site start giving error like
sqlcode =*-23326*  sqlerrm=*ORA-23326: object group "PUBLIC"."MYREPGRP" is quiesced*it means if i stop replication my database will not work while i am using asynchronous
replication.
i want my master database to work in any situation either replication is working or not.
Thnaks

Answer 1

Make sure the replication object you want to drop really exists.
check dba_repobject and dba_objects views.
select sname, oname, type, status, gname
from dba_repobject
where oname='AC_CHECK'
[pre]select owner, object_name, object_type
from dba_objects
where object_name='AC_CHECK'
Regarding ORA-23326.
This error occurs if the replication status is QUIESCED and you want to execute DML transaction against a replicated object.
While the replication status is QUIESCED no DML transactions are allowed against the replication objects.
Usually you want to stop the replication (suspend the master activity) if you want to perform maintenance activities (drop/add rep objects). This should be done in off hours and should be planned. You should be aware that no DML transactions are allowed while the master activity is suspended.
Also be aware that when you try to suspend the activity, the database will try to push and apply all the pending transactions. This may take some time (depends on the size of the transactions). So it is good practice to make sure there are no transactions that are waiting in DEFTRANDEST queue.
If you want to read more how the QUIESCED state affects the database activity, please refer to the following link:
http://download.oracle.com/docs/cd/B19306_01/server.102/b14226/repmaster.htm#sthref260
Cheers,