Just one more way to do this - look at "Realtime database services" from Sybase (http://www.sybase.com/pro
Advantage over the above suggested solutions is more db-friendly approach - the data are extracted from Oracle transaction logs and not by trigger and pooled event tables.
Disadvantage is product cost and another vendor in solution apart Tibco and Oracle.
Main Topics
Browse All Topics





by: itsandilPosted on 2005-11-24 at 13:19:40ID: 15358163
There are atleast three ways of doing this - I can only offer you the concept behind it but actually implementing it technically is gonna take me some time though I'm sure you can figure it out.
1) The "crude" way (I know you've clearly stated discomfort at this option but it's a suggestion so I'll include it for the sake of it)
Have a cronjob/IM poller/scheduled task/ process poll for a particular change in your database, detect it and publish it over RV to a listener who writes the updated to Server B
2) The "neater" way - as you suggested, embed a Java class that publishes over RV to a listener on Server B. This is certainly feasible.
3) Go for Tibco's ADB adapter. Look it up.
Option 2 is probably the better solution for you in terms of cost and control - but if you really are looking for a sophisticated way of doing this then go for option 3.
For the sake of discussion - if data replication is your concern, why aren't we using a direct Oracle data replication? Unless your business requirement is to control this data replication on your EAI ...?