You may want to read up on Oracle Replication Manager and see if you can use
it. If you do not have it, or not excited about using it (it has many
packages), here is a nutshell of poor man's one way replication : I would
not use export since it creates a dump of all records. Use it for backups.
- On each client site, add a trigger to copy updated records to a temporary
table.
- When things are quiet, 1AM for example, have some type of "cron" job dump
the content of the table into a comma delimited file. Mark those rows as
"processed". Ship it to the server using ftp.
If you must use dial up, you need to use scripting to handle all this.
- Server runs another cron job that verifies that all the files are in
place, and apply them as an Update/insert , and create log files showing
Failure or Success. Send this file back to the client and let it delete all
the "processed" rows from the temporary table if it was a Success.
- Repeat the same following day.
"Himansu" <m.himansu_at_sify.com> wrote in message
news:33194ce2.0202062243.23825f41_at_posting.google.com...
> Thank you Jon.
> Actually the assumption here is that there won't be any duplicate data
> in the client sites.So in each client site, each table will have
> non-overlapping set of primary keys with any other site.
> Could you please let me know your idea in a lower level details.
>
> I mean your reference to "create a file with all the daily delta in a
> fixed format " is same as an export file or else ?
> And supposing we have an NT environment, can you suggest with that ?
>
> Regards...
> Himansu
>
> "Jon Yi" <jon.yi_at_verizon.net> wrote in message
news:<VMb88.287$QQ1.184566_at_paloalto-snr2.gtei.net>...
> > When you have multiple instances of a database, and then try to merge
the
> > updates on a regular interval, you will run into many tough questions
such
> > as "Which is the master? How do you update each client site?" Assuming
> > each client site will not try to overwrite each other(a Big ASSUMPTION),
you
> > can create a file with all the daily delta in a fixed format by making
it
> > run at designated time, ftp over to the server. The server must be
running a
> > program that detects the arrival of the file and apply it to its
database.
> > If you want this to occur without human input, I'd suggest using Unix
> > (Linux) on both ends. To make this work without fail (You want to make
it so
> > in business systems) will be a non-trivial task.
> > Good luck.
> >
> > "Himansu" <m.himansu_at_sify.com> wrote in message
> > news:33194ce2.0202052248.31ef0b8b_at_posting.google.com...
> > > Hello !
> > >
> > > We have a system in which the same database is running in
> > > several Client machines(desktops) on Personal Oracle.
> > > We have another machine(say server)with the same database which is
> > > connected
> > > (through dial-up network connection) to each of the client machines
> > > in different times during the day.
> > > The need is to transfer all the new transactions to the database on
> > > the server
> > > from each of the client machines when the connection is on.
> > >
> > > One approach for this as I see is to send the dmp file(incremental
> > > export)
> > > to the server each time the connection is on and then to import this
> > > file on the server.
> > > But this involves manual work at both the ends.
> > >
> > > Is there any other way in which the transactions can be updated in the
> > > server
> > > without much of manual work involved ???
> > >
> > > I need the solution early, so need your comments/suggestions soon.
> > >
> > > Thank you in advance.
> > > Himansu
Received on Thu Feb 07 2002 - 11:52:42 CST
