Comments on: How to Attach a SQL Profile to a Different Statement - Take 2

By: osborne

osborne — Fri, 23 Oct 2009 16:51:55 +0000

Fikret,

Please email me the statements and the plans and the hints associated with the Profile and I’ll have a look.

Kerry

By: Fikret

Fikret — Fri, 23 Oct 2009 12:07:16 +0000

I have a query when I execute it oracle does not use index. when i use index hint in query works very fine and i want that oracle use my hint. and i created whth mov_sql_profile.sql and i saw that plan changed. And plan shows that it uses index. But in really not using because when i use manually that query with hint it is running quickly but when i remove hint at this time plan not changed but works very hard as it is plan not this plan.
Please sorry for my bad English

By: osborne

osborne — Fri, 23 Oct 2009 08:35:56 +0000

Fikret,

I’m not sure I understood your question. If you can provide more details I’ll be happy to to take a look.

Kerry

By: Fikret

Fikret — Fri, 23 Oct 2009 06:10:37 +0000

Hi I want to ask one question again move_sql_profile.sql works fine. I changed plan for my sql with move_sql_profile but query works slowly again. when i use my query with hint it works fine but the plan is the same

By: Blogroll Report 09/10/2009-16/10/2009 « Coskan’s Approach to Oracle

Blogroll Report 09/10/2009-16/10/2009 « Coskan’s Approach to Oracle — Wed, 21 Oct 2009 23:28:55 +0000

[...] Kerry Osborne-How to Attach a SQL Profile to a Different Statement – Take 2 [...]

By: osborne

osborne — Wed, 21 Oct 2009 22:47:26 +0000

No problem. Happens to me all the time (usually I figure out my mistake right after I post something). ;)

Kerry

By: Coskan

Coskan — Wed, 21 Oct 2009 15:58:50 +0000

It was my fault that I was using the same sqlid for the moved one everything works fine :)

By: osborne

osborne — Mon, 19 Oct 2009 16:38:42 +0000

Thanks for the comments Coskan.

On the first suggestion, I think v$sqlarea should only return one row per sql_id. I don’t recall ever seeing more than one row for a statement in that view. It’s possible I have a typo somewhere using v$sql which has a row for every child. Please send the error you got and I’ll do a little more looking.

On the second one, that error should only show up if there is an existing SQL Profile already on that statement. Let me know if that is not the case and we’ll figure out what’s going on.

Also, I just this morning modified the move_sql_profile.sql script to allow it to work for 10g or 11g, so you might want to grab that new version instead of having separate versions for 10g and 11g.

Thanks again for the comments.

Kerry

By: Coskan

Coskan — Mon, 19 Oct 2009 16:08:05 +0000

Hi Kerry,

Very nice post thank you very much for sharing.
Couple of things for the scripts
1- move_sql_profile
select
sql_fulltext
into
cl_sql_text
from
v$sqlarea
where
sql_id = ‘&&sql_id’

this can return more than 1 when you have multiple children so rownum should be used to avoid the fetch error.

2- Maybe I am missing some step but on both 11G and 10G I am having “ORA-13830: SQL profile with category DEFAULT already exists for this SQL statement” when I run move_sql_profile or move_sql_profile11(which I created as the same way of sql_profile11 script you use)

By: osborne

osborne — Mon, 19 Oct 2009 14:55:44 +0000

Sorry about that Fikret. The version I originally put up only worked with 10g. That was an oversight on my part (I forgot that 11g modified the layout of the underlying SQL Profile structures). I have modified the move_sql_profiles.sql script to work with either version. Please let me know if you have any further issues.

Kerry