AQ Nightmare

From: Brady, Mark <Mark.Brady_at_Constellation.Com>
Date: Mon, 22 Dec 2008 16:44:13 -0500
Message-ID: <1BB5C9CF81E4FB4F8FFED437AA3E5D635CEEC4638F@EXM-OMF-02.Ceg.Corp.Net>

So I want to queue some "invoice" data and propagate it to another server.

Of course, like most invoices, it contains one header object and a nested table of detail objects. Whoa... Can't queue an object with a nested table. Seems like a pretty lame limitation but anyways...

The work around is to change the queue to be grouping by transaction. Change the queuing to queue a stream of ANYDATA objects then wrap the header and details and queue them, then commit. This works ok, until you try to propagate them and I hit a bug in that won't let ANYDATA propagate. DBA's don't want to go to where the bug is fixed because .3 is our standard.

Ok, so fine, I can't get the queues to propagate. So I'll just Dequeue over a dblink. Nope, can't do that either because you can't reference Objects over DBLinks.

Then someone suggested you can reference objects on more than one server by manually setting the OID. So we try that and still no joy. You can't reference an object over a dblink.

But I'm thinking that Propagation does it, somehow. Propagation manages to get an object from one server to another. How does it do it?

Any hints besides attempting to convince the DBA's to upgrade would be appreciated.

>>> This e-mail and any attachments are confidential, may contain legal,
professional or other privileged information, and are intended solely for the addressee. If you are not the intended recipient, do not use the information in this e-mail in any way, delete this e-mail and notify the sender. CEG-IP2

Received on Mon Dec 22 2008 - 15:44:13 CST

Original text of this message