I have had a couple of private responses on this as well a couple to the list Firstly I should have typed ASMM (Automatic Shared memory Mananagment) rather than ASSM. I knew what I meant but I bet I am not the first one to make that mistake Secondly the CPU count is either 2,4, or 8 depending on which server I try it on. Not really sure what line is being taken on that one Finally I have been informed that the log_buffer shares a memory granule with the fixed SGA. That had crossed my mind but I had not been able to track any supporting evidence down. Thanks for the responses and the input John _____ From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Hallas, John, Tech Dev Sent: 07 June 2006 15:05 To: oracle-l@xxxxxxxxxxxxx Subject: log_buffer value does not match spfile value I have a number of 10G databases where the value of log_buffer in the spfile is not the same as the value within the instance. Oracle is obviously deciding it's own value. This is the same on systems using ASSM and not (sga_target) The documentation does not seem to support this but I am sure from a number of instances that this is happening. Any ideas on this. Nothing much coming from Metalink. I believe that this is also happening on a databases using an init.ora file rather than an spfile Thanks John SQL> show parameter log_buffer NAME TYPE VALUE ------------------------------------ ----------- ------------------------------ log_buffer integer 2097152 SQL> show parameter spfile NAME TYPE VALUE ------------------------------------ ----------- ------------------------------ spfile string /WELDBPROD/u01/oradata/GMSDB/s pfileGMSDB.ora SQL> !strings /WELDBPROD/u01/oradata/GMSDB/spfileGMSDB.ora | grep -i log_buffer *.log_buffer=32768 SQL> show parameter sga_target NAME TYPE VALUE ------------------------------------ ----------- ------------------------------ sga_target big integer 512M