On 29/04/2007, at 12:29 PM, Jeff Victor wrote:

Dedhi Sujatmiko wrote:
Hi Irlando,
my answers inline,
Q6.Are there any other types of issues with zones?

1. Do not limit the memory usage of Oracle using rcapd. It just does not

This is not true. It works, but you must understand the memory needs of Oracle, and you must understand how Solaris accounts for memory.

This statement is incorrect for currently shipping versions of Solaris 10. As stated by the previous poster, rcapd should _not_ be used with databases.

The reason is that it does not understand shared memory so the accounting is inaccurate. A fixed version has made it into Nevada, and should show up in Solaris 10 Update 4.


2. Cannot use Oracle DISM, but of course, what for?

This was true until Solaris 10 11/06. With that release we added support for configurable privileges. The global zone admin can assign the privilege PROC_LOCK_MEMORY to a zone which needs to use DISM. With that privilege, Oracle can use DISM.

If you do that, you might want to also use the resource control project.max-device-locked-memory to cap Oracle's use of locked memory. Whether you use the latter feature depends on how much you trust Oracle and how fast the DB will grow.

---------------------------------------------------------------------- ---- Jeff VICTOR Sun Microsystems jeff.victor @ sun.com
OS Ambassador            Sr. Technical Specialist
Solaris 10 Zones FAQ: http://www.opensolaris.org/os/community/ zones/faq ---------------------------------------------------------------------- ----
zones-discuss mailing list

zones-discuss mailing list

Reply via email to