UIM: Conditionmanager.Createconditions API Causes Performance Issue When Used In Loop Within 1 Transaction And Business Interaction
(Doc ID 1341033.1)
Last updated on FEBRUARY 03, 2019
Applies to:Oracle Communications Unified Inventory Management - Version 7.1.2 to 7.1.2 [Release 7.1.2]
Information in this document applies to any platform.
When createConditions() is called in loop, part of single Transaction, then the SQL that got executed in the previous call get executed again in next call of createConditions() method, so if you have 100 ports to put condition then for the first port SQL will be executed 100 times, for second port 99times and so on.
This leads to performance degradation.
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