Did you try cursor_sharing=force?

Regards,

Waleed

-----Original Message-----
Sent: Thursday, July 26, 2001 5:37 AM
To: Multiple recipients of list ORACLE-L


list, 
this application heavyly make use of literals , NO BIND VARIABLES
and was running without any lib cache latch or shared pool latch problems on
7.3.2

We ported the DB to 8.1.5 and v$session_wait is full of "latch free" event
!!
all the latch waits are on lib cache and shapred pool (as expected from any
app NOT using bind vars) 
and the app is running terribly  slow !!

my question is... how 7.3.2 was able to handle this ?? how i explain this to
my management ?
i was able to convince then on porting to 8i to get better perfornace !! 

note: i cannot change the app. all changes must be from the back end.

TIA

Rahul

-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- 
Author: Rahul
  INET: [EMAIL PROTECTED]

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).
-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- 
Author: Khedr, Waleed
  INET: [EMAIL PROTECTED]

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).

Reply via email to