RE: Accessing ASH is slow
From: Mark W. Farnham <mwf_at_rsiz.com>
Date: Tue, 23 Jul 2013 16:36:52 -0400
Message-ID: <042301ce87e4$5e36b560$1aa42020$_at_rsiz.com>
It should not affect the answer (except possibly the ordering of the reported set), but it can affect whether or not an index can be used in projecting the join.
Date: Tue, 23 Jul 2013 16:36:52 -0400
Message-ID: <042301ce87e4$5e36b560$1aa42020$_at_rsiz.com>
It should not affect the answer (except possibly the ordering of the reported set), but it can affect whether or not an index can be used in projecting the join.
From: Henry Poras [mailto:hrp_at_google.com]
Sent: Tuesday, July 23, 2013 3:13 PM
To: mwf_at_rsiz.com
Cc: usn_at_usn-it.de; ORACLE-L
Subject: Re: Accessing ASH is slow
Martin,
Maybe I'm missing something here, but why would the NLSSORT setting impact the join condition? Wouldn't the outcome of the join equality be the same regardless of the sort setting?
Henry
-- http://www.freelists.org/webpage/oracle-lReceived on Tue Jul 23 2013 - 22:36:52 CEST