Oracle may work best with SCHED_NOAGE scheduling policy

回复 收藏
本帖最后由 spain.yx 于 2011-11-16 18:05 编辑

Oracle may work best with SCHED_NOAGE scheduling policy

When setting this parameter to the highest fixed priorities  

hpux_sched_noage=178 (for HP/UX 11i  without RAC)


ORACLE DOC
This could be suited to online transaction processing (OLTP) environments
because OLTP environments can cause competition for critical resources.

Overall performance improvements of 5 to 10% for OLTP applications.

If the parameter setting is out of range, Oracle sets the parameter to a
permissible value and continues with the SCHED_NOAGE policy with the new value.
It also generates a message in the alert_sid.log file about the new setting.
Oracle Corporation recommends that you set the parameter to the required
priority level for Oracle processes


SAP Note

Ensure that the privileges RTPRIO and RTSCHED are assigned to the dba group.

1. Log on to the database server as user "root".

2. Open the file /etc/privgroup with a text editor. If this file does not exist, create it.

3. Add the following entry to this file so that the two privileges are assigned to the dba group with every system start:
dba RTPRIO RTSCHED

4. Save the changes and exit the editor. Execute the following command to assign the privileges to the dba group on an ad-hoc basis (without a restart):
/usr/sbin/setprivgrp -f /etc/privgroup

5. The privileges should now be assigned correctly. The following call should now return RTPRIO and RTSCHED:
/usr/sbin/getprivgrp dba

The next time you start the database, warnings regarding RTSCHED and RTPRIO should no longer be written to the alert log.
2011-11-16 17:42 举报
已邀请:

回复帖子,请先登录注册

退出全屏模式 全屏模式 回复
评分
可选评分理由: