Re: Aq and wls 8
- From: Ujang Jaenudin <ujang.jaenudin@xxxxxxxxx>
- To: Niall Litchfield <niall.litchfield@xxxxxxxxx>
- Date: Mon, 8 Feb 2010 20:15:34 +0700
niall,
from oracle 10.2 streams training material
"Buffered message enqueue and
dequeue operations are much faster than persistent message operations
because, optimally, there
is no disk access. Also, unlike persistent message operations, no redo is
written to disk."
looks nice, right?
anyone has observed this?
On Mon, Feb 8, 2010 at 7:21 PM, Niall Litchfield <niall.litchfield@xxxxxxxxx
> wrote:
> On Mon, Feb 8, 2010 at 10:33 AM, Ujang Jaenudin
> <ujang.jaenudin@xxxxxxxxx>wrote:
>
>> Nigel,
>>
>> in the oracle aq there is queue buffer, I think the commit mechanism
>> differ than ordinary tables.... CMIIW
>>
> why exactly do you think the commit method is different? The storage of the
> messages is different from storage of data in heap segments for sure,
> but why do you think that adding work to a transaction means that
> less information will need to be logged about the transaction to ensure
> consistency and recoverability?
>
>
>> I think also more Efficient if mdb in during dequeue jms and insert to
>> table can be batched, BUt developer said it too many effort....
>>
>>
>
> I'm not sure what you are trying to say here? If you have a batch system
> that you are processing one item at a time then likely that is the design
> error. If you are trying to batch auditing of single transactions then that
> must surely present a risk that a transaction or transactions won't get
> audited.
>
>
> --
>
> thanks and regards
> ujang | oracle dba | mysql dba
> jakarta - indonesia
> --
> //www.freelists.org/webpage/oracle-l
>
>
>
>
>
> --
> Niall Litchfield
> Oracle DBA
> http://www.orawin.info
>
--
thanks and regards
ujang | oracle dba | mysql dba
jakarta - indonesia
Other related posts:
