If I'm not mistaken, log_buffer will be automagically sized at instance startup if using ASMM, effectively ignoring the setting of the log_buffer parameter. This is eluded to in the paragraph below your reference: "The memory allocated to these pools [including log_buffer] is deducted from the total available for SGA_TARGET when Automatic Shared Memory Management computes the values of the automatically tuned memory pools." Also see MeatLink 373018.1. Someone please correct me if I'm wrong. (be gentle!) Rich > BTW The log buffer is not managed by the Automatic Shared Memory Management > in 10gR2: > > http://download.oracle.com/docs/cd/B19306_01/server.102/b14237/initparams192.htm > > "The following pools are manually sized components and are not > affected by Automatic Shared Memory Management: > * Log buffer -- //www.freelists.org/webpage/oracle-l