To cater for dynamic SGA reallocation, the memory is managed in "granules". Above a certain total size of SGA the granule size is 16M on most platforms. 64M is 4 granules - if you want to use something closer to 50M you will have to go for 48M. Regards Jonathan Lewis http://www.jlcomp.demon.co.uk The Co-operative Oracle Users' FAQ http://www.jlcomp.demon.co.uk/faq/ind_faq.html April 2004 Iceland June 2004 UK - Optimising Oracle Seminar ----- Original Message ----- From: "Kommareddy, Srinivas (MED, Wissen Infotech)" <Srinivas.Kommareddy@xxxxxxxxxx> To: <oracle-l@xxxxxxxxxxxxx> Sent: Thursday, March 18, 2004 5:44 PM Subject: strange issue with java_pool_size : Hi All, : : OS: solaris 2.8 : DB: 9i (9.2.0.3) : : When we set java_pool_size to 50M (52428800) in init.ora and bounce the db, : it is showing the value as 64M (67108864). : : Can somebody throough some light on this ? : : Has anyone encountered this situation ? (any other parameters effecting this : ?) : : Thanks and Regards, : Srinivas : : ---------------------------------------------------------------- Please see the official ORACLE-L FAQ: http://www.orafaq.com ---------------------------------------------------------------- To unsubscribe send email to: oracle-l-request@xxxxxxxxxxxxx put 'unsubscribe' in the subject line. -- Archives are at //www.freelists.org/archives/oracle-l/ FAQ is at //www.freelists.org/help/fom-serve/cache/1.html -----------------------------------------------------------------