RE: Strange error when resizing MEMORY_TARGET

From: Mark W. Farnham <>
Date: Tue, 15 Jan 2013 11:35:51 -0500
Message-ID: <013a01cdf33e$62dbb420$28931c60$>

Good answer. I would only add that it is easy to miss that Oracle really means "target" not "limit" which has probably led to your confusion.

After you find the lowest setting it will swallow, you *might* want to increase your target to that if what you're after is more generous start-up values and less dynamic allocation. If you're already at 20 and you need more, that is going to require a bounce.

If your memory is currently oscillating by just a few granules between shared_pool and buffer_cache, you *might* want to add a little room and set both to the ceilings of their respective oscillations and turn off automatic resizing as much as you can when you eventually get the chance.

-----Original Message-----
From: [] On Behalf Of Stefano Cislaghi
Sent: Tuesday, January 15, 2013 2:21 AM
Cc: Oracle Discussion List
Subject: Re: Strange error when resizing MEMORY_TARGET

On 15 January 2013 08:15, De DBA <> wrote:
> ORA-00846
Hi Tony,
this is a known behaviour. Check your v$memory_resize_ops . You should see that the sum of sga and pga is greater than 16gb. This is the reason of the message. Oracle needs in fact to decrease memory. For more info, if you have MoS access, check also note: 452512.1 and 139783.1



The SQLServerAgent service depends on the MSSQLServer service, which has
failed due to the following error: The operation completed successfully.


Received on Tue Jan 15 2013 - 17:35:51 CET

Original text of this message