We are in 8.1.7.0 and the bug 2225065 is not there.
From: Jesse, Rich [EMAIL PROTECTED]
Date: Sat, 28 Sep 2002 08:27:34 -0500
Subject: RE: Setting Cursor Sharing = Force in 8.1.7.3
Nat,
We are currently using CS=F on 8.1.7.2 and we'll be patching to 8.1.7.4
soon. You need to be made
Nat,
We are currently using CS=F on 8.1.7.2 and we'll be patching to 8.1.7.4
soon. You need to be made aware of some severe problems with this in 8i.
We've run across BUG 2225065 listed on MetaLink. It says that you can
actually get incorrect results in certain queries when using CS=F.
Nat
You may want to take a look at:
http://www.interealm.com/roby/technotes/cursor_sharing.html
Dennis Williams
DBA
Lifetouch, Inc.
[EMAIL PROTECTED]
-Original Message-
Sent: Friday, September 27, 2002 3:13 PM
To: Multiple recipients of list ORACLE-L
We are looking into setting up
I went thru this recently ...
The best thing to do is to FORCE the developers to use
bind variables and then this is no longer an issue.
If you do set it to FORCE , I believe there is a problem
with it in versions 8.1.6 and before and it should not be
used.Double Check with Metalink on
Make them use bind variables. Even if cursor_sharing did work correctly
(it might in 8.1.7, but I don't remember), using bind variables will
relieve the Oracle kernel of a lot of work (i.e., response time).
Cary Millsap
Hotsos Enterprises, Ltd.
http://www.hotsos.com
Upcoming events:
- Hotsos
I recently used it on 8.1.7.4 and 9i.
I gained 33% performance gain. It would be different depending on how
much literal SQL is used in your code.
My process ran fine, and I was able to load the data. However, I have
not fully checked the data yet.
Shakir
--- Johnson, Michael [EMAIL
Title: RE: Setting Cursor Sharing = Force in 8.1.7.3
We had problems with FORCE setting on 901x. The query it was changing to bind variables was
select to_char(sysdate,:b1)
from dual
/
Now :b1 is a format mask supplied by developer. Initially it would work fine and then start throwing
