Selective Replication



Scenario: Have two schemas (A and A_HIST) in the same database. A is
used for currents (old data gets deleted) an A_HIST is used to capture
data from A. Data never gets deleted from A_HIST. So A_HIST is currents
and all the historic data too used for reporting.

Current Implementation: Using Triggers on 20 tables in A to replicate
insert and updates to A_HIST tables.

Problem: I want to reduce the resource overhead (latches) of triggers
and have flexibility of possibly have the A_HIST schema in a different
database. I know database links on the triggers will provide this
flexibility but all SQL and data changes are already captured in the
redo and archive logs so Advanced Replication (using streams) should be
faster, right?

Trotting though the documentation I can not determine if it is possible
to only replicate INSERT, UPDATE and MERGE statements over the
replicated schema using Advanced Replication, has anyone done this
before? Had a quick search on asktom too, no luck.

Resources available: AIX 5.3, 10.2.0.1 (soon 10.2.0.2) and RAC

I'm open for other solutions too.

Thank you in advance

Regards
Bernard

.



Relevant Pages

  • Re: STREAMS capture and propagate to different schema
    ... can anyone say definitively if i can or can't capture and propagate an ... object owned by one schema and apply that to a different schema on the ... as in a.dept (source database) changes captured and propagated to ... Daniel A. Morgan ...
    (comp.databases.oracle.server)
  • Re: STREAMS capture and propagate to different schema
    ... can anyone say definitively if i can or can't capture and propagate an ... object owned by one schema and apply that to a different schema on the ... as in a.dept (source database) changes captured and propagated to ...
    (comp.databases.oracle.server)
  • Sync shema independently of data????
    ... We have a large database with many foreign keys that we would like to ... replicate the schema and the data separately. ... Function code, but have not yet found a way to replicate the Table, ...
    (microsoft.public.sqlserver.replication)
  • Re: STREAMS capture and propagate to different schema
    ... can anyone say definitively if i can or can't capture and propagate an ... object owned by one schema and apply that to a different schema on the ... as in a.dept (source database) changes captured and propagated to ...
    (comp.databases.oracle.server)
  • Re: Push subscription: "schema and data"
    ... Just so that I am very clear, if I had made a manual change to the database ... the structure change would NOT replicate. ... > schema changes for existing publications with subscriptions. ... >> When pushing a new subscription, the wizard prompts if you would like to ...
    (microsoft.public.sqlserver.replication)