When Processing Huge Volume Of Messages, RIB Server Runs 'Out Of Memory' Issues
Last updated on JANUARY 29, 2018
Applies to:Oracle Retail Integration Bus - Version 13.0 and later
Information in this document applies to any platform.
What happens when a user tries to take the existing records extracted from a Publishing application table, update/modify them in bulk and try to publish it to the other applications through Retail Integration Bus (RIB) ?
For example : A user runs a SQL query to take all the records in ITEM_SUPPLIER table and update them at a stretch, so that it will result in creation of entries in ITEM_MFQEUE table with respective RIB messages (of type Itemsupp mod) and expect that it will publish all these messages from Retail Merchandising System (RMS) to Store Inventory Management (SIM) and Warehouse Management System (RWMS)
The SQL query may be like such:
where exists (select 1 from item_master im where item_level=tran_levelAnd Status='A'and IM.ITEM=ISP.ITEM);
--XXXXXXX RECORDS updated
In short, triggering the ITEM_MFQUEUE table to get the modified ITEM_SUPPLIER records to be populated to SIM/RWMS through RIB at one go.
What happens in such cases ?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms