Solaris10 Kernel Settings for Oracle

Solaris10 (SPARC) Kernel & TCP

Settings Prescribed for the SAP

Oracle Environment

(Part 3C of Series)

Sun Project Number:Sun Document Reference:Version Number:Author:Purpose:Document Date:Internal

1.0

1.0

Scott Livezey

US Business Applications Practice

SAP CC

Technical Brief

August 1, 2006

The topic of this report is pretty self-explanatory. The purpose of this report is to provide a set of general-purpose and preferred Solaris parameters for preparing the servers to

host/support the SAP/Oracle environment.

The guidelines in this report are a combination of applying the latest options with the available technology. The contents in this report is not necessarily original, but is intended to provide a 'clearer picture' of compiling & applying what our group has recommended and will continue to recommend to our SAP customers preparing their configuration for the best combination of management and performance.

NOTE: This report should be considered as one component in addressing the 'total solution' for implementing the storage/Solaris/volume/filesystem/Oracle configuration layers preparing for SAP. Because each type and combination of storage subsystem needs to be addressed in its own way, please refer to the individual report for the storage subsystem of interest that should be combined with the contents in this report and the others.

The recommended strategy is this report has been applied in SAP environments up to and including WAS6.40 for Oracle up to and including 9i; 32-bit and 64-bit inclusive. Any modifications for adapting to the future releases of either SAP WAS (7.X) or Oracle (10g) software is not expected.

This report is the third in a series; new revision for Solaris10 with an additional section for TCP related settings. A third section has also been provided that compiles the recommended settings specific to the T2000 servers. The release of the remaining reports in this series are available as well.

(1) Solaris10 (SPARC) Kernel Settings

The kernel settings listed below are intended to provide for the most popular choices of support tools integrated with Solaris (i.e. Veritas). Many of the parameters involved are simply meant to help 'open the flood gates' regarding I/O throughput beyond the vanilla/default values. It is expected that the database server configuration supporting the SAP environment will have a minimum of 4-8CPUs and 8-10GB RAM (with emphasis on the RAM component). The server configuration for which these settings have been applied are, in many cases, much larger than this minimum (40+ CPUs, 40+GB RAM) to suit our largest customers.

NOTES: (1) What is not present below are any settings specific to supporting a particular storage subsystem (i.e. any of the sd_* or ssd_* parameters). These settings vary by the particular type of storage subsystem supported and therefore should be analyzed & added as a separate task.

Project: Internal Page 2 of 5Author : Scott Livezey

(2) Settings related to the Veritas toolset are mainly for supporting the database server domain, but can be applied to the application server domains for standardization purposes. The latest versions of VxVM software have updated most or all of

the settings below as default. But they are included to be sure.

Project: Internal T Page 3 of 5Author : Scott Livezey

Solaris10 (SPARC) Kernel & TCP Settings for the SAP Oracle Environment

(2) Recommended TCP-based Performance Settings

The following settings are mainly to address high volumes of network traffic between application servers and database servers associated with any physical 3-tier SAP architecture.

NOTE: The following ndd TCP & UDP tunings can be placed in the standard

/etc/rc2.d/S68net-tune location

Project: Internal T Page 4 of 5Author : Scott Livezey

(3) T2000-Related Solaris10 Kernel Parameters

Final Thoughts

This strategy has provided a good foundation for the customers who have implemented it (per the recommedations). In general, I have found it very difficult to provide recommendations that will work successfully 'across the board' regarding SAP/Oracle database configurations (or I think that there are many less than most have expected). But the guidelines laid out in this report (and in the others of this series) are as close as what can be provided.

Project: Internal Page 5 of 5Author : Scott Livezey