Re: What DBMS jobs and database links required for Materialized view replication?



Pressed post too soon!

My questions:

* what does dbms_repcat.do_deferred_repcat_admin do? does it co-
ordinate push and purge jobs?

* do I need a push job from the master to the snapshot site?
* if so:
- do I need to create a database link/s between the master and
the snapshot?
-who owns the database link on the master site? repadmin, public or
the schema
owner?
-how do I ensure that the purge job starts right after the push is
completed?

If I do not need the push job from the master to the snapshot site:
* how do I ensure that the snapshot logs on the master site are purged
once the refresh job issued from the mv site is completed?
* can I remove the push job on the MV site? I do not want to push
anything from the MV site unless in an emergecy when all the users
read/write to the snapshot instead of the master.

If I can have either the refresh pull job or the push master job,
which is better? Or can I have both?

Re database links
I
* do they have to have the full name of the database eg
b.mydomain.com or can I use the alias for the database as given in
tnsnames.ora

eg

any_old_name =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = MYHOST )(PORT = 1521))
)
(CONNECT_DATA =
(SERVICE_NAME = B.mydomain.com)
)
)

* How can I test if a link is working?

Thanks in advance

Edwinah63




.



Relevant Pages

  • Re: Missing INFORMATION_SCHEMA.ROUTINES
    ... When you use the object browser to look for these views, ... will only find them in the database [master], ... >I have taken a snapshot of the available views through Enterprise Manager. ...
    (microsoft.public.sqlserver.server)
  • Re: Dependency mapping
    ... John, ... If you create a master by using Insert/Projects and leaving the 'link to ... snapshot of) the files each week, ...
    (microsoft.public.project2000)
  • FW: NIM push latency
    ... on the master shows that the Cstate doesn't change from "ready for NIM ... wait (roughly 5 minutes before any events occur on the client). ... any NIM actions that I push from my master. ...
    (AIX-L)
  • trans replication of large tables...
    ... source and distributor db are on a separate RAID array's. ... records each(with column filters) ... it takes ~ 18h for the distributor agent to push the data to the subscriber. ... I have tried to recreate the snapshot once again, ...
    (microsoft.public.sqlserver.replication)
  • NIM push latency
    ... any NIM actions that I push from my master. ... Can anyone point me to what may be causing this delay before execution? ...
    (AIX-L)