Propagation Performance Degradation for Large Message Transaction Sizes from 10.2 onwards
(Doc ID 761316.1)
Last updated on FEBRUARY 12, 2019
Applies to:Oracle Database - Enterprise Edition - Version 10.2.0.1 to 22.214.171.124 [Release 10.2 to 12.1]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.
Propagation performance from a transactional queue has degraded in 10.2 compared to 9.2.
The transaction size is of the order of 1 million messages.
In 9.2 this transaction size took 30 minutes to propagate but fails to propagate in 10.2.
The job_queue_process associated with the propagation schedule consumes a large amount of CPU and memory. PGA heapdumps of the process indicate that the callheap is growing and this growth is associated with the following dequeue sql
select tab.rowid, tab.msgid, tab.corrid, tab.priority, tab.delay,
tab.expiration, tab.retry_count, tab.exception_qschema,
tab.exception_queue, tab.chain_no, tab.local_order_no, tab.enq_time,
tab.time_manager_info, tab.state, tab.enq_tid, tab.step_no,
tab.sender_name, tab.sender_address, tab.sender_protocol,
tab.dequeue_msgid, tab.user_prop, tab.user_data
"USER"."QUEUE_TABLE" tab where msgid = :1
which is executed for every dequeued message.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document