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
]]
Sent: Friday, September 27, 2002 3:13 PM
To: Multiple recipients of list ORACLE-L
Subject: Setting Cursor Sharing = Force in 8.1.7.3
We are looking into setting up cursor_sharing parameter to FORCE. Has
anyone seen any bad effects of setting Cursor_sharing=FORCE.
Are there any
real bad
We are looking into setting up cursor_sharing parameter to FORCE. Has
anyone seen any bad effects of setting Cursor_sharing=FORCE. Are there any
real bad effects of setting it..?
I was thinking of going back to my developers and make them use bind
variables in their code.
If I set the above
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
System/Database Administrator
[EMAIL PROTECTED] Quad/Tech International, Sussex, WI USA
-Original Message-
From: Binley Lim [mailto:[EMAIL PROTECTED]]
Sent: Sunday, July 28, 2002 8:48 PM
To: Multiple recipients of list ORACLE-L
Subject: RE: Cursor Sharing
, WI USA
-Original Message-
From: Johnson, Michael [mailto:[EMAIL PROTECTED]]
Sent: Thursday, July 25, 2002 7:09 PM
To: Multiple recipients of list ORACLE-L
Subject: Cursor Sharing Continued
Setting it to Force worked well as the
pool has been cleared on many queries
]]
Sent: Thursday, July 25, 2002 7:09 PM
To: Multiple recipients of list ORACLE-L
Subject: Cursor Sharing Continued
Setting it to Force worked well as the
pool has been cleared on many queries
using literals any many of those hard
parses went away. So far ... So good.
I aint
Take your case to management with that statistics
of how long queries take with and without bind
variables. Let them decide when to make the
developers re-code their apps. If your management
doesnt make them correct it then I dont know what
to say from there.My management has said It
recipients of list
ORACLE-L
[EMAIL PROTECTED]
cc:
Subject:RE: Cursor Sharing| Soft
Parsing
Well, three times, right? I think it takes three
parse calls before
session_cached_cursors begins to help. But 3 is
still O(1). Once per
: RE: Cursor Sharing| Soft Parsing
I checked the Tom Kyte site. A soft parse comprises two
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: Orr, Steve
INET: [EMAIL PROTECTED]
Fat City Network Services-- (858) 538-5051 FAX: (858) 538-5051
San Diego, California
Michael - So . . . since you have a work-around that is relatively easy from
the developer point of view, how do you plan to convince them to rewrite
their programs? Or do you have a really big hammer?
Dennis Williams
DBA
Lifetouch, Inc.
[EMAIL PROTECTED]
-Original Message-
Sent:
or not. I thought the
processing of the statement to check permissions to be soft parsing. But,
perhaps I'm misinformed.
When cursor-sharing converts a statement to use bind variables it
would
save on hard parsing, if a match were found the pool; also, it could
lessen
the number of statements
]]
Sent: Thursday, July 25, 2002 4:58 PM
To: Multiple recipients of list ORACLE-L
Subject: RE: Cursor Sharing| Soft Parsing
I checked the Tom Kyte site. A soft parse comprises two
...
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: Jesse, Rich
INET: [EMAIL
Cary Millsap [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
07/25/2002 07:58 AM
Please respond to ORACLE-L
To: Multiple recipients of list ORACLE-L
[EMAIL PROTECTED]
cc:
Subject:RE: Cursor Sharing| Soft
Parsing
Well, three times
only parse SQL statements
once if session_cached_cursors is set. Further executions of the same
SQL don't require a hard or soft parse.
Jared
When cursor-sharing converts a statement to use bind variables it would
save on hard parsing, if a match were found the pool; also, it could lessen
... where username = 'literal string'.
I PROVED to them that they were the cause of the shared pool allocation
errors by pulling the statements out of the sql area. Didn't matter, it
would have put them behind schedule. VP agreed with the programmers, I
put cursor sharing on. Solved the problem
Of course
executions of the same
SQL don't require a hard or soft parse.
Jared
When cursor-sharing converts a statement to use bind variables it
would
save on hard parsing, if a match were found the pool; also, it could
lessen
the number of statements present in the pool.
Ian MacGregor
Stanford Linear
or not.
No, code that uses bind variables need only parse SQL statements
once if session_cached_cursors is set. Further executions of the same
SQL don't require a hard or soft parse.
Jared
When cursor-sharing converts a statement to use bind variables it
would
save on hard parsing, if a match were
or not.
No, code that uses bind variables need only parse SQL statements
once if session_cached_cursors is set. Further executions of the same
SQL don't require a hard or soft parse.
Jared
When cursor-sharing converts a statement to use bind variables it would
save on hard parsing
No, code that uses bind variables need only parse SQL statements
once if session_cached_cursors is set. Further executions of the same
SQL don't require a hard or soft parse.
Hmm read somewhere (James Morle?) that this may not apply if the
(subsequent) bind variable sizes differ vastly
.
But, perhaps I'm misinformed.
When cursor-sharing converts a statement to use bind variables it would
save on hard parsing, if a match were found the pool; also, it could lessen
the number of statements present in the pool.
Ian MacGregor
Stanford Linear Accelerator Center
[EMAIL PROTECTED]
--
Please
.
When cursor-sharing converts a statement to use bind variables it would
save on hard parsing, if a match were found the pool; also, it could lessen
the number of statements present in the pool.
Ian MacGregor
Stanford Linear Accelerator Center
[EMAIL PROTECTED]
--
Please see the official ORACLE
of the statement to check permissions to be soft parsing. But,
perhaps I'm misinformed.
When cursor-sharing converts a statement to use bind variables it would
save on hard parsing, if a match were found the pool; also, it could lessen
the number of statements present in the pool.
Ian MacGregor
statement has permissions to run it. It has to do this
every time a statement is run, bind variables or not. I thought the
processing of the statement to check permissions to be soft parsing. But,
perhaps I'm misinformed.
When cursor-sharing converts a statement to use bind variables
Setting it to Force worked well as the
pool has been cleared on many queries
using literals any many of those hard
parses went away. So far ... So good.
I aint sayin nothin to the developers
although some have already noticed an
improvement.
I am going to put the hammer down on
them to
a statement is run, bind variables or not. I thought the
processing of the statement to check permissions to be soft parsing. But,
perhaps I'm misinformed.
When cursor-sharing converts a statement to use bind variables it
would
save on hard parsing, if a match were found the pool; also, it could
:RE: Cursor Sharing| Soft Parsing
Well, three times, right? I think it takes three parse calls before
session_cached_cursors begins to help. But 3 is still O(1). Once per
call is O(#executions).
Cary Millsap
Hotsos Enterprises, Ltd.
http://www.hotsos.com
Upcoming events:
- Hotsos Clinic
Has anyone set Cursor Sharing to Force ?
I have a new system that we have to support
and there is alot literals filling up the
pool.I have never changed this parameter
from the default as many seemed to think the
jury was still out on it. However, due to
my situation, I figured I would try
at the
instance level (my boss is reading my copy, so I can't give you page #s).
- Kirti
-Original Message-
Sent: Wednesday, July 24, 2002 6:08 PM
To: Multiple recipients of list ORACLE-L
Has anyone set Cursor Sharing to Force ?
I have a new system that we have to support
and cursor sharing at
http://technet.oracle.com/deploy/performance/pdf/cursor.pdf
So CURSOR sharing is not the silver bullet as one may expect.
Regards
Suhen
On Thu, 25 Jul 2002 10:23, you wrote:
Mike,
What is the version of the database? Some versions of 8.1.7 had a few bugs
when
views in using this parameter at the
instance level (my boss is reading my copy, so I can't give you page #s).
- Kirti
-Original Message-
Sent: Wednesday, July 24, 2002 6:08 PM
To: Multiple recipients of list ORACLE-L
Has anyone set Cursor Sharing to Force ?
I have a new system
I'm misinformed.
When cursor-sharing converts a statement to use bind variables it would save on
hard parsing, if a match were found the pool; also, it could lessen the number of
statements present in the pool.
Ian MacGregor
Stanford Linear Accelerator Center
[EMAIL PROTECTED]
-Original
).
- Kirti
-Original Message-
Sent: Wednesday, July 24, 2002 6:08 PM
To: Multiple recipients of list ORACLE-L
Has anyone set Cursor Sharing to Force ?
I have a new system that we have to support
and there is alot literals filling up the
pool.I have never changed this parameter
from
).
- Kirti
-Original Message-
Sent: Wednesday, July 24, 2002 6:08 PM
To: Multiple recipients of list ORACLE-L
Has anyone set Cursor Sharing to Force ?
I have a new system that we have to support
and there is alot literals filling up the
pool.I have never changed this parameter
from
submitting a SQL statement has permissions to run it. It has to do this
every time a statement is run, bind variables or not. I thought the
processing of the statement to check permissions to be soft parsing. But,
perhaps I'm misinformed.
When cursor-sharing converts a statement to use bind
39 matches
Mail list logo
