CSS is an essential component of ASM installations as it is required to syncrohize ASM resources and ASM crashes in the absence of CSS component.
When there is any OS resource saturation (ie, CPU, memory shortage, etc), CSS sometimes could not obtain the OS resource and thus determines there is a problem and abort itself. A solution for this issue is to add more CPU/memory resources to the server or to move resource intensive applications (grid control, etc.) and some databases to another server to consume less resources on this server.
Another workaround is to bump up the CSS misscount. This will give the OS more time to recover before css eviction. The purpose of this note is to document the steps needed to modify the CSS misscount in single instance ASM installations.
Those steps should NOT be followed for RAC installations. Please follow Note 284752.1 to see the steps needed to modify the CSS misscount in 10g RAC environment. Please also review Note 294430.1 to understand the implications before editing misscount settings.
Steps to increase CSS process miscount to 300 (5 minutes).
1) Shut down all ASM instances and DB instances depending on ASM.
2) Run $ORACLE_HOME/bin/localconfig delete to remove the existing CSS configuration.
3) Edit the $ORACLE_HOME/bin/localconfig file and look for the CLSCFG invocation, it should look something like this:
$CLSCFG -local -o $CH -l "AMERICAN_AMERICA.WE8ISO8859P1"
At the end of the line, add trace and misscount params as follows:
#Create CSS keys only if needed to
$CLSCFG -local -o $CH -l "AMERICAN_AMERICA.WE8ISO8859P1" -misscount 300
4) Re-add CSS by running $ORACLE_HOME/bin/localconfig add.
5) Restart ASM and DB instances.
来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/29953799/viewspace-1873093/，如需转载，请注明出处，否则将追究法律责任。