I don't have an explanation, but:
The CBO uses floating point instructions a lot (I think). May be there is a
difference in rounding between the Intel chip and the Sparc chip that causes
the cost to differ just enough so that the index isn't/is used.
Anjo.
On Saturday 07 September 2002 01:4
Interesting. This might explain a similar problem
I had a few years ago. Oracle support did not
have a good answer for it.
Jared
On Friday 06 September 2002 13:43, Toepke, Kevin M wrote:
> I the RBO, the order the indexes were created in is important! I was able
> to show this to management
oer
[mailto:[EMAIL PROTECTED]]Sent: Friday, September 06, 2002
3:28 PMTo: Multiple recipients of list ORACLE-LSubject:
RE: Same SQL statement, Same Oracle, Different OS ==> Different
E
(see answer below)
> -Original Message- >
From: Sam Bootsma [mailto:[EMAIL PROTECTED]
Title: RE: Same SQL statement, Same Oracle, Different OS ==> Different Expla
(see answer below)
> -Original Message-
> From: Sam Bootsma [mailto:[EMAIL PROTECTED]]
>
> One of our developers is encountering a situation where
> Oracle 9.0.x explain
> plan chooses one index when on UN
