Message propagated doesn't dequeue
edited Feb 17, 2010 9:58PM in GoldenGate, Streams and Distributed Database (MOSC) 4 commentsAnswered
Hi folks,
I have the following situation: I have a queue Q_OUT where
applications will put messages. A Propagation P_OUT_TO_IN will
retrieve these messages and send them to another queue,
Q_IN, from which others applications will read.
During my tests I came across something strange: when Q_OUT
and Q_IN are in the same DB instance, the message in Q_OUT stays
there forever, even after being propagated. "That's OK", I
thought, because the associated queue table is of the type Multiple
Consumers (as demanded by the creation of the Propagation).
But, when Q_OUT and Q_IN are located in different instances (and the
I have the following situation: I have a queue Q_OUT where
applications will put messages. A Propagation P_OUT_TO_IN will
retrieve these messages and send them to another queue,
Q_IN, from which others applications will read.
During my tests I came across something strange: when Q_OUT
and Q_IN are in the same DB instance, the message in Q_OUT stays
there forever, even after being propagated. "That's OK", I
thought, because the associated queue table is of the type Multiple
Consumers (as demanded by the creation of the Propagation).
But, when Q_OUT and Q_IN are located in different instances (and the
0