Oracle AQ EnqueueTime not correctly available

[Leonardo-Ferreira]

I'm dequeuing messages from my oracle AQ but the property "EnqueueTime" does not have the milliseconds portion of it! How can I retrieve it?

[alexkeh]

EnqueueTime returns a DateTime type. It should include a placeholder for milliseconds. Is the issue that the milliseconds placeholder contains just zeros?

Is this question about unmanaged, managed, or core ODP.NET? Which ODP.NET version?

[Leonardo-Ferreira]

Hello @alexkeh, thanks for the interest.

The issue is that the milliseconds part is always zero.

I'm using Oracle.ManagedDataAccess.Core v23.7.0

[alexkeh]

The ODP.NET dev team did some more research into this question. The DB AQ enqueue time granularity is in seconds only. Thus, ODP.NET cannot provide the millisecond information since the DB doesn't provide it.

Once the DB provides millisecond data, ODP.NET AQ should act as a passthrough and be able to return it.

[Leonardo-Ferreira]

@alexkeh, but the DB has a timestamp column with 9 digits precision:

https://docs.oracle.com/en/database/oracle/oracle-database/19/adque/aq-messaging-gateway-views.html#GUID-78CC1D99-D2DD-4B80-BC38-4BBF39E05EFA

[alexkeh]

@Leonardo-Ferreira
I see. ODP.NET supports the ENQ_TIME, but not the ENQ_TIMESTAMP. I've filed ER 37767276 to track this request. ODP.NET would probably provide a second enqueue time property for the millisecond granularity.

Can you provide a short business case on the need and urgency for the feature? I'll add the info to the ER.

[Leonardo-Ferreira]

In general lines, we have a financial authorizer that runs atop of oracle, and the "Your purchase was approved/denied" messages are made available to the other platforms via AQ.
Because more and more platforms are now requiring these messages and our Oracle instance is critical, we decided to change the pattern, and now, only a single app reads from AQ and moves those messages to a more friendly and specialized service like RabbitMQ and Azure Service Bus. This app is called "AQ-Bridged".
One very important metric that we must output is the amount of time that a message sat there on AQ waiting to be read. We call this "Latency" and we calculate this by subtracting the current timestamp from the EnqueueTime, hence why we need the timestamp as precise as possible.

If you require more details, can you share your email @alexkeh? I can't send more details on a public place

[alexkeh]

You can email the team using dotnet_us(at)oracle.com.