Re: What DBMS jobs and database links required for Materialized view replication?
- From: Edwinah63 <edwinah@xxxxxxxxxxxxxxxxxxx>
- Date: 30 May 2007 22:38:51 -0700
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
.
- Follow-Ups:
- References:
- Prev by Date: What DBMS jobs and database links required for Materialized view replication?
- Next by Date: Re: ORacle non-graphical Install
- Previous by thread: What DBMS jobs and database links required for Materialized view replication?
- Next by thread: Re: What DBMS jobs and database links required for Materialized view replication?
- Index(es):
Relevant Pages
|