I am looking at Oracle's DBCN API (Continuous Query Notification) and using it implement a stream of events indicating new and/or modified rows in the database.
What I am concerned about is this: If I configure and start a change listener and then my java client fails, the server side is still accumulating changes for delivery. However, when my java client resumes, my options appear to be limited:
So how can I resume a session with an existing registration ? Alternatively, from where might I find and retrieve the backlogged notifications ?
Thanks.
//Nicholas
You could implement a server side solution (PL/SQL) that will put all changes into a queue (Oracle Advanced Queue). Then your java client could connect against this queue and get the changes.
If your client fails, the changes will still get written into the queue on the server. And when you resume your client it will get all changes from the queue, resuming from the last you received.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With