Re: AW: Temp usage on Linux vs solaris

With regard to plan hash values the plan hash value calculation has changed 
between 10.2 on Big Endian Systems and 11.2 on Little Endian Systems.
So even if the plan is the same the plan hash value will not be the same and you 
will have to do a string comparison of all steps.

A workaround to get the same plans is to use

Set "_cursor_plan_hash_version"=2 on the 10.2 source system. ( I have not tested 
this workaround and this might not be feasible to do)

 
Fairlie Rego
Senior Oracle Consultant
http://el-caro.blogspot.com/
M: +61 402 792 405
 




________________________________
From: Petr Novak <Petr.Novak_at_trivadis.com>
To: "greg_at_structureddata.org" <greg_at_structureddata.org>; Kumar Madduri 
<ksmadduri_at_gmail.com>
Cc: oracle Freelists <Oracle-L_at_freelists.org>
Sent: Tue, 21 June, 2011 4:28:11 PM
Subject: AW: Temp usage on Linux vs solaris

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_at_freelists.org [oracle-l-bounce@freelists.org]&quot; im 
Auftrag von &quot;Greg Rahn [greg_at_structureddata.org]
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_at_gmail.com<mailto:ksmadduri@gmail.com>> 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
--
http://www.freelists.org/webpage/oracle-l

--
http://www.freelists.org/webpage/oracle-l