There are still issues on Solaris with sga_target (which is good) and sga_max_size. The DISM patch has to be applied on the Solaris server otherwise sga_target is automatically set to whatever sga_max_size is and ideally I would want a 25% - 50% difference between these 2 John -----Original Message----- From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Christian Antognini Sent: 22 May 2006 16:28 To: lambu999@xxxxxxxxx Cc: oracle-l@xxxxxxxxxxxxx Subject: RE: SGA_TARGET in 9i Hi And in addition the log buffer and the non-default buffer caches are not automatically managed, i.e. you have to manage them yourself. HTH Chris >sga_target is new in 10g > >regards > >On 5/22/06, Ram K <lambu999@xxxxxxxxx> wrote: > > Hello, > > I searched for it on Oracle-l archives, but I could not find an answer. Has SGA management >through SGA_TARGET parameter become commonly accepted without any major problems in 9i. Does it >mean we dont have to bother any more about setting log_buffers, adjusting the log_buffers size >during a big load, buffer_cahce, setting buffer_pool_keep/recycle, shared_pool, etc even during >peak performance periods? > > Apologies if the question has been answered before. I would appreciate a link if there is >any. > > -- > Thanks, > Ram. -- //www.freelists.org/webpage/oracle-l -- //www.freelists.org/webpage/oracle-l