RE: ORA-00064: object is too large to allocate on this O/S (1,16352000)
Date: Thu, 03 Jan 2008 14:29:43 +0800
You need to increase your _ksmg_granule_size as documented in Metalink. The session array needs to fit into contiguous piece of memory (e.g. one extent/granule) for easy lookup, and your granule size is too small for given number of sessions.
I would go with 256MB granule size on Solaris 10 as this supports 256M large pages.
Note as this is an undocumented parameter, consult at least Metalink and preferrably get blessing from Oracle Support for this. This post is only for providing the information, it's not a recommendation.
-- Regards, Tanel Poder http://blog.tanelpoder.comReceived on Thu Jan 03 2008 - 00:29:43 CST
> -----Original Message-----
> From: oracle-l-bounce_at_freelists.org
> [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of VIVEK_SHARMA
> Sent: Thursday, January 03, 2008 12:49
> To: oracle-l_at_freelists.org
> Subject: ORA-00064: object is too large to allocate on this
> O/S (1,16352000)
> For a BIG Benchmark Run, on increasing the sessions to 7000
> (from 5000) getting the following ORA Error
> ORA-00064: object is too large to allocate on this O/S
> (1,16352000) NOTE - increasing of the seesions parameter is
> necessary for the Benchmark Runs.
> $ oerr ora 64
> // *Cause: An initialization parameter was set to a value
> that required
> // allocating more contiguous space than can be
> allocated on this
> // operating system.
> // *Action: Reduce the value of the initialization parameter.
> Does this point to an O.S. Kernel parameter which needs to be
> increased? if so, which?