RE: buffer advisor (has become: should there be a private sql area?)
From: Iggy Fernandez <iggy_fernandez_at_hotmail.com>
Date: Fri, 12 Sep 2014 12:09:10 -0700
Message-ID: <BLU179-W55F9278C4CDCEAA1946AE3EBCD0_at_phx.gbl>
The situation: A critical business process or even an internal Oracle process does not find room in the shared poolThe Oracle solution: Kill the critical business process or the internal Oracle process
Date: Fri, 12 Sep 2014 12:09:10 -0700
Message-ID: <BLU179-W55F9278C4CDCEAA1946AE3EBCD0_at_phx.gbl>
The situation: A critical business process or even an internal Oracle process does not find room in the shared poolThe Oracle solution: Kill the critical business process or the internal Oracle process
Why not give the customer a choice of allowing processes to operate in degraded mode? re: if it degraded all other ongoing processes, would this be a good thing or bad thing?
How would permitting a private SQL area (for use in degraded mode) degrade other ongoing processes? Iggy
Date: Fri, 12 Sep 2014 12:51:43 -0600
From: fuzzy.graybeard_at_gmail.com
To: oracle-l_at_freelists.org
Subject: Re: buffer advisor (has become: should there be a private sql area?)
On 12/09/2014 12:45 PM, Iggy Fernandez wrote: Why is "operate in degraded mode" such a bad thing? If taken in isolation, it might not be a bad thing. Perhaps even a good thing. In a multi-process/task/user system, if it degraded all other ongoing processes, would this be a good thing or bad thing? /Hans
-- http://www.freelists.org/webpage/oracle-lReceived on Fri Sep 12 2014 - 21:09:10 CEST