Hi,
I read about mv and mv logs and I am still clueless.
Are you saying, create the mv logs in the large table and
create updateable mv in the small table site?
But I dont need to record changes in the large table.
I need inserts from small to large table
large table <----< small table
mv logs are needed for fast refeshes, so i dont know if i need it at all
in the large table.
Mike
"Van Messner" (messner1_at_NOSPAMbestweb.net) writes:
> Yes, you don't understand. You will be bringing changes from the small
> table to the large table, correct? Read about materialized views and see
> where the mv log will be and read about refresh intervals. You will see
> that the mv log size should not be a problem.
>
> Van
>
>
>
> "Michel Lee" <ae299_at_FreeNet.Carleton.CA> wrote in message
> news:c9noui$4dv$1_at_freenet9.carleton.ca...
>>
>> Sybrand Bakker (gooiditweg_at_sybrandb.verwijderdit.demon.nl) writes:
>> > On 3 Jun 2004 03:35:16 GMT, ae299_at_FreeNet.Carleton.CA (Michel Lee)
>> > wrote:
>> >
>> >>
>> >>A replication question/mlml
>> >>
>> >>Hi,
>> >>I have 2 sites far apart(Asia & North America),
>> >>one with a large table , the other with a small table, same structure.
>> >>
>> >>Inserts are done in the small table.
>> >>I would like to copy this data to the large table routinely.
>> >>
>> >>(North America) large table <-----<------ small table (Asia)
>> >>
>> >>How would I do it?
>> >>I thought of a few ways but they dont really fit in.
>> >>1) MultiMaster Replication (NO)
>> >>2) Materialized view (NO)
>> >>3) Updateable Materialized view (NO)
>> >>
>> >>Maybe this is not a replication question?
>> >>This seems like a simple question, but how would I do this?
>> >>
>> >>thanks in advance
>> >>Mike
>> >
>> > Simple replication would do, no need for multimaster replication.
>> > Just set up a snapshot and a snapshot log and a snapshot refresh job.
>> > You seem to reject those solutions (looking at the 'NO' label),
>> > the alternative would be a remote insert, which is just cumbersome and
>> > unstable, compared to replication.
>>
>>
>> Hi Sybrand,
>> I am not sure what you mean about the Updateable Materialized view
>> solution. The large table will be many terabytes. So, whould
>> be materialized view log be too much over head.
>> I only want the data to be inserted from small to large table.
>> No other updates in the large table is allowed.
>> Maybe I dont understand.
>> cheers
>> Mike
>>
>> >
>> >
>> > --
>> > Sybrand Bakker, Senior Oracle DBA
>>
>>
>> --
>> /-------------------------------------------------------------------/
>> / http://miccc.com /
>> /-------------ae299_at_ncf.ca------------------------------------------/
>
>
--
/-------------------------------------------------------------------/
/ http://miccc.com /
/-------------ae299_at_ncf.ca------------------------------------------/
Received on Fri Jun 04 2004 - 00:17:47 CDT
