修改 CSS misscount，disktimeout参数

Steps To Change CSS Misscount, Reboottime and Disktimeout ( ID 284752.1)
In this Document
Purpose
Scope
Details
A. 10.2.0.1 without the fix of bug 4896338
B. 10.2.0.1 with the fix of bug 4896338, 10.2.0.2 to 11.1.0.7
C. 11gR2
References
APPLIES TO:
Oracle Database - Enterprise Edition
Information in this document applies to any platform.
PURPOSE
The purpose of this note is to document the steps needed to modify the CSS misscount, reboottime and disktimeout
settings. Please review Note 294430.1 to understand the implications before editing these settings.
SCOPE
Customers should NOT modify CSS settings unless guided by either Oracle support or Oracle development to do so.
DETAILS
A. 10.2.0.1 without the fix of bug 4896338
1) Shut down CRS on all but one node. For exact steps use note 309542.1
2) Execute crsctl as root to modify the misscount:
$CRS_HOME/bin/crsctl set css misscount <n> #### where <n> is the maximum private network latency in
seconds
3) Reboot the node where adjustment was made
4) Start all other nodes which was shutdown in step 1
5) Execute crsctl as root to confirm the change:
$CRS_HOME/bin/crsctl get css misscount
B. 10.2.0.1 with the fix of bug 4896338, 10.2.0.2 to 11.1.0.7
With the fix of bug 4896338 (available on top of 10.2.0.1, fixed in 10.2.0.2 and 10.1.0.6 patch set), there are two
additional settings that can be tuned.
** reboottime (default 3 seconds) - the amount of time allowed for a node to complete a reboot after the CSS daemon
has been evicted. (I.E. how long does it take for the machine to completely shutdown when you do a reboot)
** disktimeout (default 200 seconds) - the maximum amount of time allowed for a voting file I/O to complete; if this
time is exceeded the voting disk will be marked as offline. Note that this is also the amount of time that will be
284752.1 1/2
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=iud8jvsjm_3... 2016/6/15
required for initial cluster formation, i.e. when no nodes have previously been up and in a cluster.
1) Shut down CRS on all but one node. For exact steps use note 309542.1
2) Execute crsctl as root to modify the misscount:
$CRS_HOME/bin/crsctl set css misscount <n> #### where <n> is the maximum private network latency in
seconds
$CRS_HOME/bin/crsctl set css reboottime <r> [-force] #### (<r> is seconds)
$CRS_HOME/bin/crsctl set css disktimeout <d> [-force] #### (<d> is seconds)
3) Reboot the node where adjustment was made
4) Start all other nodes which was shutdown in step 1
5) Execute crsctl as root to confirm the change:
$CRS_HOME/bin/crsctl get css misscount
$CRS_HOME/bin/crsctl get css reboottime
$CRS_HOME/bin/crsctl get css disktimeout
C. 11gR2
With 11gR2, these settings can be changed online without taking any node down:
1) Execute crsctl as root to modify the misscount:
$CRS_HOME/bin/crsctl set css misscount <n> #### where <n> is the maximum private network latency in
seconds
$CRS_HOME/bin/crsctl set css reboottime <r> [-force] #### (<r> is seconds)
$CRS_HOME/bin/crsctl set css disktimeout <d> [-force] #### (<d> is seconds)
2) Execute crsctl as root to confirm the change:
$CRS_HOME/bin/crsctl get css misscount
$CRS_HOME/bin/crsctl get css reboottime
$CRS_HOME/bin/crsctl get css disktimeout
REFERENCES
BUG:4896338 - PLACEHOLDER BUG FOR PCW 10.2.0.1 MERGE FOR VERY LOW BROWNOUT - 10.2
NOTE:294430.1 - CSS Timeout Computation in Oracle Clusterware
NOTE:309542.1 - How to start/stop the 10g/11g Oracle Clusterware
?
284752.1 2/2
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=iud8jvsjm_3... 2016/6/15