Re: 9i Parsing Optimization


I don't know what technology Siebel Tools uses,
but your earlier double call may have been a
"feature" of the ODBC or JDBC or whatever
driver was between Siebel and Oracle, rather
than a bit of the application code.

I believe there used to be a feature in the Perl
driver, for example, that made it do a parse call without bind values, followed by an execute
call with bind values - but if the bind types weren't
all character, the execute call would require a second parse call. It's something like that that may have gone away on the upgrade.

Don't ask me to quote specifics - it's a long time
ago and in another version.


Regards

Jonathan Lewis
http://www.oracle.com/technology/community/oracle_ace/ace1.html#lewis

The Co-operative Oracle Users' FAQ
http://www.jlcomp.demon.co.uk/faq/ind_faq.html

Cost Based Oracle: Fundamentals
http://www.jlcomp.demon.co.uk/cbo_book/ind_book.html


----- Original Message ----- From: "amonte" <ax.mount@xxxxxxxxx>
To: <jonathan@xxxxxxxxxxxxxxxxxx>
Cc: <oracle-l@xxxxxxxxxxxxx>
Sent: Wednesday, August 30, 2006 9:50 PM
Subject: Re: 9i Parsing Optimization


Anjo and Brandon, I forgot to mention we use RULE BASED OPTIMIZER so
permutations shouldnt be a problem. This is not PL/SQL so it cant be some
pl/sql optimization. This is a Siebel Workflow Manager Process.

Jonathan, it is Siebel Tools, I understand that from application codes you
can invoke two parse calls but what I dont understand is why the second call
is not "called" in 9i?

TIA

Alex 

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


Other related posts: