After Applying Fix for Bug 10126772, There Are Issues With the Polling Timer Query
Last updated on AUGUST 17, 2016
Applies to:Oracle Retail Store Inventory Management - Version 13.1 and later
Information in this document applies to any platform.
***Checked for relevance on 9-Sep-2013***
After upgrading to SIM 18.104.22.168 and applying the fix for <Bug 10126772>, the following issues are encountered with the polling timer query:
1. The Staging Table query blocks messages with the same Business ID, regardless of Message Family. <Bug 10126772> addressed the problem that messages could be processed out of order because the sequence ID produced IDs out of order (due to running on Oracle RAC and the way the sequence DDL was defined).
The fix was to always process Create Message Types before other messages with the same Business ID. The updated query matches on Business ID, but fails to take into account Message Family. A common implementation of Business ID is to return the ID of the messages item, making it is entirely possible that there are other messages with the same Business ID but in a different Message Family.
2. A consequence of issue 1 is that what was previously a minor issue is now a major issue. Message processing blocks on NULL Business IDs, regardless of Message Family. The contract for Business ID was that a NULL ID signified that no blocking was required. Now, with the changes for <Bug 10126772>, it appears that a message with a NULL Business ID can block other messages that also have a NULL ID. Many messages have a NULL Business ID.
This problem is triggered by application of the fix for <Bug 10126772>.
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 hundreds of Community platforms