Skip to Content
avatar image
Former Member

Best Practices for SAP on Oracle 11 Zones

Let me preface by saying, I'm not a Solaris admin, I'm on the SAP BASIS side.

We run our SAP (BW, ERP, SCM, etc) all on Oracle 11.3 sparse zones. Currently every zone shares all of the resources. By that I mean, each zone sees the full compliment of processors, RAM, ect contained in the global. My gut tells me that this is not best practice and that we should have things setup in a more "partitioned" fashion. But I'm not a Solaris expert. We've had cases where some processes on one zone will commandeer the entire global and we'll have to end up taking a hard reboot of a global because we're not able to login to a zone and shut anything down gracefully. As a DBA, this give me grey hair. I think to myself that surely there must be a way to segregate the resources between the zones so that one zone can't kill an entire global. BUT, I don't want to give up performance by removing processing power from my zones.

Can anyone share some best practices with me? I know there are some SAP Notes concerning some of this, but nothing that comes right out and tells me bluntly that we should or shouldn't be assigning procs/memory directly to zones or domains.


Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

0 Answers