From: <>
Date: Tue, 22 Jan 2013 13:11:10 -0600
Message-ID: <>

It's a system on a 3-node RAC (with 4 databases & 12 instances).


-----Original Message-----
From: Andy Gmail [] Sent: Tuesday, January 22, 2013 1:05 PM
To: Taylor Christopher - Nashville
Cc: <>
Subject: Re: CURSOR_SHARING survey

I have done this in 9i and 10gr2. What version are you looking at? The symptom we fixed was very high parse CPU (the sysadmin swore the cpu's were going to melt), 100% CPU usage and run queues at about 20 on a 4 CPU system. It did fix that problem, though we ended up having to work around several other bugs.

Sent from my iPhone

On Jan 22, 2013, at 11:43 AM, <> wrote:

> I'm curious how many of you guys have set CURSOR_SHARING=FORCE from EXACT in a development or test database (or even production) and what led you to set it?
> My only experience with CURSOR_SHARING comes from my PeopleSoft days when SIMILAR was thought to be a "good" thing and then found out it wasn't (at least I believe that's the way it went).
> I've never played around with FORCE.
> The reason I'm asking is that we have 4 QA instances that share the same server and one of these QA boxes has the requirement to match production as far as memory pools, parameters etc.
> This has the adverse effect of forcing the other 3 into smaller RAM buckets. I'm getting 4031 errors intermittently and [of course] it's related to non-shared sql blowing my sql area and library cache sizes all to he**.
> (Keeping in mind this is a very immature application - much work going on in redesign - while that is happening though I really would like to keep the 4031 errors down to a minimum)
> Regards,
> Chris Taylor
> Oracle DBA
> Parallon IT&S
> --

Received on Tue Jan 22 2013 - 20:11:10 CET

Original text of this message