Question Solved but another question is there
Satender Dalal, August 24, 2016 - 11:19 am UTC
Hi Tom,
I have gone through the document which you have provided. That was useful.
There if you see one Plan was Disabled.
So if i drop the disabled plan, will that also be the same thing.
In my case i have 2 plans already, so i have a option to load only one hash plan in Base line
So can i go with loading only one plan.
August 25, 2016 - 3:14 am UTC
Yes, if you have both plans loaded into the baseline, then all you need to do is disable the bad one. The other one will be the one that the optimizer then uses.
Execution hash value of one sql_id to another sql_id?
Dana, July 20, 2017 - 10:00 pm UTC
I have a scenario where tables are highly volatile, and suffer from rather frequent changes in execution times.
Most are in the form of:
insert into table t (list_of_columns) (select [list_of_columns] from table y where id=:b1);
When I can pre-set/pre-run stats, and run a similar query with a literal value like:
insert into table t (list_of_columns) (select [list_of_columns] from table y where id=999);
I get a execution time measured in seconds.
With bind variables, and stats not up to date, execution times range from minutes to days.
I have captured both good baseline and not so good baselines using DBMS_SPM. Since I used literal values in the second query, it has a different SQL_ID from the first query.
SQL_HANDLE is also different.
My question is this. Is there a way to transfer the execution plan from the good baseline to the not so good baseline?
Thank you for your time.
Forgot version ...
Dana, July 20, 2017 - 10:14 pm UTC
My prior review/follow up is for AIX Oracle version 12.1.0.2.0.
Sorry for the omission.