Call now: 252-767-6166  
Oracle Training Oracle Support Development Oracle Apps

 
 Home
 E-mail Us
 Oracle Articles
New Oracle Articles


 Oracle Training
 Oracle Tips

 Oracle Forum
 Class Catalog


 Remote DBA
 Oracle Tuning
 Emergency 911
 RAC Support
 Apps Support
 Analysis
 Design
 Implementation
 Oracle Support


 SQL Tuning
 Security

 Oracle UNIX
 Oracle Linux
 Monitoring
 Remote s
upport
 Remote plans
 Remote
services
 Application Server

 Applications
 Oracle Forms
 Oracle Portal
 App Upgrades
 SQL Server
 Oracle Concepts
 Software Support

 Remote S
upport  
 Development  

 Implementation


 Consulting Staff
 Consulting Prices
 Help Wanted!

 


 Oracle Posters
 Oracle Books

 Oracle Scripts
 Ion
 Excel-DB  

Don Burleson Blog 


 

 

 


 

 

 
 

ORA-23357: the propagator does not exist tips

Oracle Database Tips by Donald BurlesonDecember 21, 2015

Question: I'm trying to define a propagator for a materialized view and I'm getting the "ORA-23357: the propagator does not exist" error:

SQL> BEGIN
2 DBMS_REPCAT.CREATE_MVIEW_REPOBJECT (
3 gname => 'emp_repg',
4 sname => 'SCOTT',
5 oname => 'EMP',
6 type => 'SNAPSHOT',
7 min_communication => TRUE);
8 END;
9 /
BEGIN
*
ERROR at line 1:
ORA-23357: the propagator does not exist
 

How do I check the status of materialized view propagators?

Answer:  Please see Col. Garmany's notes on defining a replication propagator for a materialized view, especially the part about the repadmin user.  Also see these notes on creating materialized view refresh groups.

The docs note this on the ORA-23357 error, a generic note that the propagator is missing:

ORA-23357: the propagator does not exist

Cause: The propagator does not exist.

Action: Register a new propagator.

On the remote site, replication is administered by repadmin. Repadmin is the snapshot administrator, the propagator, and the refresher. A database link connects repadmin with repproxy. Using a private link restricts user access to the base tables on the master site. Repproxy is granted rights to the objects being replicated. Repadmin (on the remote site) contacts repproxy and pushes changes, which repproxy applies. Oracle provides these views for monitoring replication:

DBA_REPSCHEMA. This view contains details for the replication schema.

DBA_REPCATLOG. This view provides a log of all replication activities.

DBA_JOBS. Use this view to monitor all scheduled job in the database.

DBA_REPCAT. This view shows the replication catalog.

ALL_REPCONFLICT. This view provides a list of all replication conflicts.

ALL_REPRESOLUTION. For systems defined with pre-defined conflict resolution, this view lists the resolution of every conflict.

DBA_REPOBJECT. This view gives you a list of al replicated objects.

DBA_REPSITES. This view provides is a list of replicated sites.
 

This query can check the status of the MV propagator:

select
   username,
   status,
   date_created
from
   defpropagator;

Also, these scripts check the staus of replication:

connect repadmin/repadmin
set pages 50000
col sname      format a20 head "SchemaName"
col masterdef  format a10 head "MasterDef?"
col oname      format a20 head "ObjectName"
col gname      format a20 head "GroupName"
col object     format a35 trunc
col dblink     format a35 head "DBLink"
col message    format a25
col broken     format a6 head "Broken?"
prompt Replication schemas/ sites
select 
  sname, 
  masterdef, 
  dblink
from
  sys.dba_repschema;
prompt RepCat Log (after a while you should see no entries):
select 
   request, 
   status, 
   message, 
   errnum
from
   sys.dba_repcatlog;
prompt Entries in the job queue
select 
   job, 
   last_date, 
   last_sec, 
   next_date, 
   next_sec, 
   broken, 
   failures,
   what
from
   sys.dba_jobs
where
   schema_user = 'REPADMIN';
prompt Replication Status:
select 
   sname, 
   master, 
   status
from
   sys.dba_repcat;
prompt Returns all conflict resolution methods
select * from all_repconflict;
prompt Returns all resolution methods in use
select * from all_represolution;
prompt Objects registered for replication
select 
   gname, 
   type||' '||sname||'.'||oname object, 
   status
from
   sys.dba_repobject;
select * from dba_repsites;

 

For more details and working scripts to define replication, see the books on Oracle Replication and Oracle Streams.
 

If you like Oracle tuning, you might enjoy my book "Oracle Tuning: The Definitive Reference", with 950 pages of tuning tips and scripts. 

You can buy it direct from the publisher for 30%-off and get instant access to the code depot of Oracle tuning scripts.


 

 

��  
 
 
Oracle Training at Sea
 
 
 
 
oracle dba poster
 

 
Follow us on Twitter 
 
Oracle performance tuning software 
 
Oracle Linux poster
 
 
 

 

Burleson is the American Team

Note: This Oracle documentation was created as a support and Oracle training reference for use by our DBA performance tuning consulting professionals.  Feel free to ask questions on our Oracle forum.

Verify experience! Anyone considering using the services of an Oracle support expert should independently investigate their credentials and experience, and not rely on advertisements and self-proclaimed expertise. All legitimate Oracle experts publish their Oracle qualifications.

Errata?  Oracle technology is changing and we strive to update our BC Oracle support information.  If you find an error or have a suggestion for improving our content, we would appreciate your feedback.  Just  e-mail:  

and include the URL for the page.


                    









Burleson Consulting

The Oracle of Database Support

Oracle Performance Tuning

Remote DBA Services


 

Copyright © 1996 -  2020

All rights reserved by Burleson

Oracle ® is the registered trademark of Oracle Corporation.