Re: Strange error when resizing MEMORY_TARGET

From: Mark Burgess <mark_at_burgess-consulting.com.au>
Date: Thu, 17 Jan 2013 09:51:31 +1100
Message-ID: <CAHn_qA72Wb6s0nbYO7OsUH=9k+ca54pUJ=TE6jV_XGgR410TXw_at_mail.gmail.com>

Hi Tony,
how many CPU's does the database see? If this is Solaris on the T-Series servers its possible that there is a minimum sizing on some of the SGA components based on the number of CPU's that the database can see. There is a discussion in MOS note # 1097866.1 around this. My previous experience with this issue was just with the SGA_TARGET setting - i'm not sure if this also applies when using MEMORY_TARGET.

Regards,

Mark

On 17 January 2013 09:17, CRISLER, JON A <JC1706_at_att.com> wrote:

> I don't work on Solaris that much, but on Linux this would be mapped
> against /dev/shm- if /dev/shm was only set to less than 20gb you would run
> into odd errors. Also, are you trying to mix hugepages and ASMM together?
> Perhaps there is a limit and its not allowing enough hugepages to be
> allocated. In linux you cannot mix hugepages and /dev/shm together but I
> think you can in Solaris.
>
>

--
http://www.freelists.org/webpage/oracle-l

Received on Wed Jan 16 2013 - 23:51:31 CET