Sayan,
Thank you for the suggestion on the force_match for the SQL Profile. I
tried that using your script but it doesn't appear to be working (also
tried the COE from SQLT which is pretty much the same thing). It looks
like the FORCE_MATCHING_SIGNATURE is NOT the same so that's obviously
causing a problem with it not using the SQL Profile.
I need to gather some additional information but have too many tasks and
work "context switching" that is not making this a productive exercise!
I'll report back with any additional findings as I get them.
Alfredo
On Wed, Feb 21, 2018 at 10:42 AM, Sayan Malakshinov <xt.and.r@xxxxxxxxx>
wrote:
Hi Alfredo,
You can create SQL Profile with parameter force_match => true, in this
case oracle will use this sql profile for the queries with the
same FORCE_MATCHING_SIGNATURE.
You can use execute this script https://github.com/
xtender/xt_scripts/blob/master/profiles/create_sql_profile_lc.sql and
input current SQL_ID.
