| Disabling hash_join_enabled [message #292368] |
Tue, 08 January 2008 15:29  |
enelson
Messages: 7
Registered: January 2008
|
Junior Member |
|
|
We have encountered bug 4401437 and Oracle's solution from note 360811.1 is to set the hash_join_enabled database property from true to false.
Has anyone else done this? What performance loss/gain did you see?
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Re: Disabling hash_join_enabled [message #292892 is a reply to message #292687] |
Thu, 10 January 2008 02:23  |
skooman
Messages: 913
Registered: March 2005
Location: Netherlands
|
Senior Member |
|
|
Are you sure the bug number you mention is correct? Did you encounter an ORA-00600 error using an connect by prior and start with statement? In EBS?
Furthermore, the doc id you mention says to add a 'no_filtering' hint to the query, not to alter any database parameters as far as I can see. Since you can't add hints to standard EBS code, I would recommend to raise an SR on Metalink for your EBS error and let support handle it.
|
|
|
|
| Re: Disabling hash_join_enabled [message #293000 is a reply to message #292892] |
Thu, 10 January 2008 09:14 |
enelson
Messages: 7
Registered: January 2008
|
Junior Member |
|
|
Thank you for your reply. The SR I opened with Oracle said the only solution for a 9.2.0.7 db is to disable the Hash_Join_Enabled parameter.
We have been running with this parameter enabled for some months and am satisfied with the application and conc requests performance.
Our concern is the impact to our system's performance if we disable this parameter.
Has anyone been running EBS with this parameter disabled on a 9.2.0.7 database?
|
|
|
|
| Re: Disabling hash_join_enabled [message #296279 is a reply to message #293000] |
Fri, 25 January 2008 09:10 |
enelson
Messages: 7
Registered: January 2008
|
Junior Member |
|
|
A follow-up...
Oracle would not backport their bug-fix for the hash_join_enabled issue to 9.2.0.7.
Disabling this join criteria would cause issues in other aspects of the system (particularly sales order lines).
We decided to rewrite an inefficient query that was called when the Credit Management Update Case Folder button was pressed. Once we rewrote the query to limit the amount of data that had to be parsed, the db engine did not utilize the hash_join because it's cost was too high. This fixed our problem for now.
BTW...all queries for the HTML based Oracle applications are in XML files (for 11.5.10 anyways).
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
