My Oracle Support Banner

JMS Messages Delivered by ODI 12c to the Queue are Not Present after Commit Step (Doc ID 2300685.1)

Last updated on AUGUST 21, 2023

Applies to:

Oracle Data Integrator - Version and later
Oracle Data Integrator on Marketplace - Version and later
Oracle Data Integrator Cloud Service - Version 17.2.1 and later
Data Integration Platform Cloud - Version and later
Information in this document applies to any platform.
The issue can occur for any JMS Queue type and ODI 12c version.


When using a Java Messaging Service (JMS) Queue as a mapping destination in Oracle Data Integrator (ODI) 12c, the data is pulled from the database using IKM SQL to JMS Append. The process completes with no errors and the log records that the records are inserted into the queue as confirmed by the insert step record count. However, the commit step count is at zero records, indicating that the commit is not occurring.

The queue files are disappearing from the destination in a very short time without being consumed, even though there are no listeners enabled for consumption on the JMS side. IKM attribute JMSEXPIRATION is set to zero, which should cause the files to remain present in the location until they are consumed.

The JMS Queue is confirmed to work via a Test, and there are no errors reported in the Operator log.

The issue can occur for any JMS Queue type and ODI 12c version.




To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.