Dat_modelselector: The Sql Statement That Loads The Configuration Contains Literals Instead Of Bind
(Doc ID 1436491.1)
Last updated on JUNE 12, 2018
Applies to:Oracle Communications Billing and Revenue Management - Version 22.214.171.124.0 to 126.96.36.199.0 [Release 7.4.0]
Information in this document applies to any platform.
***Checked for relevance on 20-May-15***
The DAT_ModelSelector loads its configuration from the Pipeline Manager Database running some SQL statements that contain literals instead of bind variables.
The statement that must be reparsed for every selector rule is like:
SELECT t15596.selector_detail FROM ifw_selector_rule_lnk t15596 WHERE t15596.selector_rule = 119369 AND NOT t15596.selector_detail IS NULL
A configuration may contain a lot of selector rules that fills up the shared pool with a lot of "one-off" SQL.
The below report Displays SQL Using more than 10 Mb of the Shared Pool:
Workaround: alter the sessions with cursor_sharing=force every time the user that loads the Pipeline configurations connects to the DB (using a trigger after LOGON on database).
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!