Oracle databases require shared memory for the different Oracle processes to access the SGA for the database. You should have enough physical memory to host each shared memory segment for your databases. By setting this, you prevent each database instance from consuming as much of the free heap as they can which will prevent additional instances from starting. So setting this is important. As for what to set it to, you should allocate enough to each zone for the database that's contained inside while staying within the physical memory limits. So it'll depend on what you have available and what each database requires.
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* Octave J. Orgeron Solaris Virtualization Architect and Consultant Web: http://unixconsole.blogspot.com E-Mail: unixcons...@yahoo.com *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* ----- Original Message ---- From: Ian Garbutt <ian.g.garb...@newcastle.gov.uk> To: sysadmin-discuss@opensolaris.org Sent: Tue, November 23, 2010 4:26:24 AM Subject: [sysadmin-discuss] Zones zone.max-shm-memory setting. Hello experts, I'm after a bit help on the above. We have a number of zones with the above being set. When the systems were built we were told that its a setting to stop the oracle databases using up all the memory. When I look into zone.max-shm-memory all I get is that its a limit on shared memory, but what is it actually limiting and is it required after all? and if it is required what should it be set as? ie half the zones RAM etc. Many thanks in advance. Ian -- This message posted from opensolaris.org _______________________________________________ sysadmin-discuss mailing list sysadmin-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/sysadmin-discuss _______________________________________________ sysadmin-discuss mailing list sysadmin-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/sysadmin-discuss
