Home » RDBMS Server » Performance Tuning » finding changed sql plans
|
Re: finding changed sql plans [message #539665 is a reply to message #539664] |
Tue, 17 January 2012 13:08   |
 |
LNossov
Messages: 318 Registered: July 2011 Location: Germany
|
Senior Member |
|
|
The only thing, I understood, you use OPTIMIZER_CAPTURE_SQL_PLAN_BASELINES=TRUE (for what purpose?). The both of SQL Plan Baselines from your output have accepted=NO, so they cannot be applied at all.
Only the first of SQL Plan Baselines for each sql gets accepted=YES, if you use automatic capturing. So if you dropped one baseline and solved your issue, this baseline should have had accepted=YES. After that the others baselines have accepted=NO and cannot be aplied anymore (unless you set accepted=YES manually).
I suggest you to turn off automatic capturing completely.
[Updated on: Tue, 17 January 2012 13:12] Report message to a moderator
|
|
|
|
Re: finding changed sql plans [message #539670 is a reply to message #539667] |
Tue, 17 January 2012 14:43   |
 |
LNossov
Messages: 318 Registered: July 2011 Location: Germany
|
Senior Member |
|
|
Automatic capturing was active in the past, because of origin=AUTO-CAPTURE for all of the baselines.
Regarding your questions.
1. yes, if all baselines are automatically generated. You can find out the "first" baselines also by
select SIGNATURE, SQL_HANDLE, PLAN_NAME from dba_sql_plan_baselines where (SIGNATURE,CREATED) in (select SIGNATURE,min(CREATED) from dba_sql_plan_baselines group by SIGNATURE);
2. yes,
3. automatic capturing is already turned off,
4. baselines with accepted=no cannot be applied. So you don't need to remove them.
You wrote Quote:I found a SQL plan was
changed and it caused performance issues
How did you find that?
[Updated on: Tue, 17 January 2012 14:44] Report message to a moderator
|
|
|
|
Goto Forum:
Current Time: Mon Jul 14 02:42:11 CDT 2025
|