AW: Temp usage on Linux vs solaris
- From: Petr Novak <Petr.Novak@xxxxxxxxxxxx>
- To: "greg@xxxxxxxxxxxxxxxxxx" <greg@xxxxxxxxxxxxxxxxxx>, Kumar Madduri <ksmadduri@xxxxxxxxx>
- Date: Tue, 21 Jun 2011 06:28:11 +0000
Plan_hash_value depends also on endianness. If the old and new system has
different endian , you would need to compare all steps of execution plans to
be sure, if the execution plan really changed.
Best Regards,
Petr
________________________________________
Von: oracle-l-bounce@xxxxxxxxxxxxx [oracle-l-bounce@xxxxxxxxxxxxx]" im
Auftrag von "Greg Rahn [greg@xxxxxxxxxxxxxxxxxx]
Gesendet: Dienstag, 21. Juni 2011 08:10
Bis: Kumar Madduri
Cc: oracle Freelists
Betreff: Re: Temp usage on Linux vs solaris
Recommendations on triaging:
1) What are the parameter differences (anything that could impact execution
plans)
2) For a given query with the issue, look at the before and after plans and
try and figure out what is causing this (get a 10053 trace and diff it)
Once you get #2 and look into the cause for the diff, then it can be analyzed
on what could be causing it.
Understand that the increased temp usage is the effect (symptom) of plans
changing and you want to get to the root cause of why that is the case.
If you have AWR data for both systems you can look at {sql_id,
plan_hash_values} comparisons assuming all the objects are identical.
On Mon, Jun 20, 2011 at 10:35 PM, Kumar Madduri
<ksmadduri@xxxxxxxxx<mailto:ksmadduri@xxxxxxxxx>> wrote:
To minimize issues with version differences we maintained the version of rdbms
s (11.1.0.7) between solaris and linux and another change to init.ora was not
to use memory_target and memory_max-target (that should not matter I hope in
this particular case thoug h. We are using sga_target and sga_max_size )
--
Regards,
Greg Rahn
http://structureddata.org
--
//www.freelists.org/webpage/oracle-l
Other related posts:
