Re: Force matching and SQL plan management

Jonathan Lewis addresses this specific question in his blog, here: http://jonathanlewis.wordpress.com/2010/01/12/force_match/

Hope that helps,

-Mark

From: Abdul Mohammed <oracle.blog3_at_gmail.com<mailto:oracle.blog3_at_gmail.com>> Reply-To: "oracle.blog3_at_gmail.com<mailto:oracle.blog3_at_gmail.com>" <oracle.blog3_at_gmail.com<mailto:oracle.blog3_at_gmail.com>> Date: Friday, November 22, 2013 at 8:09 PM To: "oracle-l_at_freelists.org<mailto:oracle-l_at_freelists.org>" <oracle-l_at_freelists.org<mailto:oracle-l_at_freelists.org>> Subject: Force matching and SQL plan management

Hello all,

I am trying to fix a hard parsing issue for database, Code on the app cannot be changed. So i was thinking to make use of SQL Profiles and use force_match=true...there are couple of SQL that are troublesome. Same SQL but uses literal values, so when i create a SQL PROFILE and put force_match=true(from what i understand, i believe this profile will be used)...my question is

1. Would putting this in place avoid hard parsing or would it still go though the hard parse phase(even with profile is set). Do note the signature(force_matching_signature is same for this type of SQL)
2. Can this be done with SQL Plan Baseline, as i rather use Baseline instead of profile. As Baseline seems to work for me in the past and profile sometimes do not work.

Any feedback is appreciated.

Thanks,

Sent from my Windows Phone

--

http://www.freelists.org/webpage/oracle-l Received on Sat Nov 23 2013 - 03:24:59 CET