RE: SQL Profile in Oracle Glossary - is this actually correct?

From: Stefan Koehler <contact_at_soocs.de>
Date: Fri, 17 Jun 2016 10:41:54 +0200 (CEST)
Message-ID: <253428152.296246.1466152914669.JavaMail.open-xchange_at_app03.ox.hosteurope.de>


Hey Jonathan,
thank you for reminding about the 500 characters limit. I almost always forget it as never hit it :)  

Best Regards
Stefan Koehler

Freelance Oracle performance consultant and researcher Homepage: http://www.soocs.de
Twitter: _at_OracleSK

> Jonathan Lewis <jonathan_at_jlcomp.demon.co.uk> hat am 17. Juni 2016 um 09:54 geschrieben:
>
> Stefan,
>
> The drawback to SQL Patches is that they're limited to 500 characters - which is sufficient for many cases, or as a temporary fix, or for the cases
> where you're not trying to fix the path but want (e.g.) to fix a degree of parallelism or disable a particular optimizer feature for a specific
> query.
>
> My preferred method is to hint the problem SQL to the path I want then capture a proper baseline that connects the unhinted SQL to the plan for the
> hinted SQL using one of the "load baseline from cursor cache" procedures that's documented in the manual.
>
>
> Regards
> Jonathan Lewis
> http://jonathanlewis.wordpress.com
> _at_jloracle

--
http://www.freelists.org/webpage/oracle-l
Received on Fri Jun 17 2016 - 10:41:54 CEST

Original text of this message