RE: ORA-00064: object is too large to allocate on this O/S (1,16352000)
From: VIVEK_SHARMA <VIVEK_SHARMA_at_infosys.com>
Date: Thu, 3 Jan 2008 12:18:16 +0530
Message-ID: <69E1360E54B50C4A828A136C158E4742036A70761E@BLRKECMBX02.ad.infosys.com>
From: Tanel Poder [tanel.poder.003_at_mail.ee] Sent: Thursday, January 03, 2008 11:59 AM To: VIVEK_SHARMA; oracle-l_at_freelists.org Subject: RE: ORA-00064: object is too large to allocate on this O/S (1,16352000)
Date: Thu, 3 Jan 2008 12:18:16 +0530
Message-ID: <69E1360E54B50C4A828A136C158E4742036A70761E@BLRKECMBX02.ad.infosys.com>
Thanks Tanel for responding & the support
In init.ora (at Production - Solaris 9/Oracle 9.2):-
sessions=25000
_ksmg_granule_size=33554432
Cheers
From: Tanel Poder [tanel.poder.003_at_mail.ee] Sent: Thursday, January 03, 2008 11:59 AM To: VIVEK_SHARMA; oracle-l_at_freelists.org Subject: RE: ORA-00064: object is too large to allocate on this O/S (1,16352000)
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:48:16 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)
>
>
> Folks
>
> 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?
**************** CAUTION - Disclaimer ***************** This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely for the use of the addressee(s). If you are not the intended recipient, please notify the sender by e-mail and delete the original message. Further, you are not to copy, disclose, or distribute this e-mail or its contents to any other person and any such actions are unlawful. This e-mail may contain viruses. Infosys has taken every reasonable precaution to minimize this risk, but is not liable for any damage you may sustain as a result of any virus in this e-mail. You should carry out your own virus checks before opening the e-mail or attachment. Infosys reserves the right to monitor and review the content of all messages sent to or from this e-mail address. Messages sent to or from this e-mail address may be stored on the Infosys e-mail system. ***INFOSYS******** End of Disclaimer ********INFOSYS*** -- http://www.freelists.org/webpage/oracle-l