![]() At times, many of our applications need to be notified of certain specific changes to this common set of data. These set of tables are used by almost all the applications in our system for mainly query purposes(common set of data strctures). This schema is actually a central repository at our site. ![]() To elaborate more on the requirement, We have a Oracle server that has Insert/Update/Delete activity going on throughout the day. Is this a viable solution for this kind of problem?Īre there other alternatives that you can suggest?Ĭan you elaborate a bit as to how we could use replcation to our advantage in this situation?Ĭurrently, we are using replcation in some of our applications heavily, but somehow, I'm not able to comprehend how would we be able to make use of it in this particular situation? This will free the triggers from making remote DML statement(s) and avoid several potential issues. We would design a standard way of constructing the AQ message so that the sender and recepient both know what is being sent and what is being received. What we are thinking is that we will setup the AQ environment and enable propagation and then the triggers will just ENQUEUE the statements into the AQ queue and Oracle will handle the propagation of this message to the remote server (if remote site was down, AQ propagation will be able to handle and recover from it), and upon receipt, the remote server will apply the changes that trigger initiated. The DML statements that we issue from the triggers can be applied asynchronously. ![]() We are looking into using AQ to solve the problem of triggers failing because of these issues. At times we get timeout errors or the remote server is not available. Currently we have several triggers that perform insert/updates to the remote servers.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |