Weird OPTIMIZER behavior for SQL*Net queries

From: Jerzy Tomasik <jerzy_at_tus.ssi1.com>
Date: Fri, 03 Sep 1999 21:53:07 -0700
Message-ID: <37D0A5B2.BC9E5FE6@tus.ssi1.com>

Hi,

I'm seeing a strange performance problem. The same query performs very well when executed
with a direct connection (e.g. sqlplus scott/tiger) and very poorly when executed through SQL*Net
(e.g. sqlplus scott/tiger_at_mydb). Running the analyzer shows that the execution path is different in
both cases.
BTW, the query generates virtually no network traffic (returns just a count).

Is there any way I can control or force the optimizer to behave the same way for a query
coming through SQL*Net as it does for local queries? I've read the docs about the hints, etc, but I haven't seen anything that seems to be the answer.

TIA, -Jerzy Received on Fri Sep 03 1999 - 23:53:07 CDT