OSwatcher on Exadata

OSwatcher is a script tool recommended by Oracle for OS-level running status detection. Exadata is installed by default.

But how does Exadata automatically start OSwatcher after the system starts? How can we modify OSwatcher parameters to adjust monitoring and log storage policies?

This article describes how to modify OSwatcher parameters from system startup to OSwatcher running, script calls in the middle, and how to modify OSwatcher parameters.

1. First, check the rc. local file to find/etc/rc. d/rc. Oracle. Exadata.

# vi /etc/rc.d/rc.local-----------------------------------------########### BEGIN DO NOT REMOVE Added by Oracle Exadata ###########if [ -x /etc/rc.d/rc.Oracle.Exadata ]; then  . /etc/rc.d/rc.Oracle.Exadata <<<<<<<<<<<<<<<<<<<<<<This script will be run automaticlly, when the OS startsfi########### END DO NOT REMOVE Added by Oracle Exadata ###########-----------------------------------------

2. Check rc. Oracle. Exadata and find/opt/oracle. cellos/vldrun-all.

# vi /etc/rc.d/rc.Oracle.Exadata-----------------------------------------# Perform validations step/opt/oracle.cellos/vldrun -all <<<<<<<<<<<<<<<<<<<<<<This script will be run automaticlly, when the OS starts-----------------------------------------

3. Check the current OSwatcher settings, collect logs every 15 seconds, and save the generated logs for 168 hours for 7 days). The bzip2 compression mode has a maximum log size of 3 GB.

# ps -ef | grep OSWroot 15962 1 0 04:00 pts/1 00:00:00 /bin/ksh ./OSWatcher.sh 15 168 bzip2 3root 15994 15962 0 04:00 pts/1 00:00:00 /bin/ksh ./OSWatcherFM.sh 168 3root 16272 9529 0 04:00 pts/1 00:00:00 grep OSW

4. The script/opt/oracle. cellos/vldrun will call the oswatcher script to start oswatcher.

# ls -al /opt/oracle.cellos/validations/init.d/oswatcher-r-xr-x--- 1 root root 5128 Aug 19 03:39 oswatcher# chmod 750 oswatcher <<<<<<<<<<<<<<<<<<<<<<<<Change the right, then we can edit it as per our expected.# ls -al oswatcher-rwxr-x--- 1 root root 5128 Aug 19 03:39 oswatcher

5. Check the settings in the current oswatcher script, and modify this modification to save the original 3G-Max log size to 4G)

# vi oswatcher----------------------------------------fi(umask 0037; nohup ./startOSW.sh 15 168 bzip2 4 >/var/log/cellos/start_oswatcher.log 2>&1 &)& <<<<<<<<<<<<change this part of the script, will let the script run as per our expected.# Dont direct logs to startosw.log. It grows too large and fast# (nohup ./startOSW.sh 15 168 bzip2 3 >/dev/null 2>&1 &)&popd >/dev/null----------------------------------------

6. Stop oswatcher

#/Opt/oracle. oswatcher/osw/stopOSW. sh # ps-ef | grep OSWroot 10528 9529 0 00:00:00 pts/1 grep OSW 7. manually start oswatcher #/opt/oracle. cellos/vldrun-script oswatcherLogging started to/var/log/cellos/validations. logCommand line is. /validations/bin/vldrun. pl-quiet-script oswatcherRun validation oswatcher-PASSEDThe each boot completed with SUCCESS

8. Check the OSwatcher settings again. The maximum log size has been changed to 4 GB.

# ps -ef|grep OSWroot 109041 1 0 03:37 pts/1 00:00:00 /bin/ksh ./OSWatcher.sh 15 168 bzip2 4root 109073 109041 0 03:37 pts/1 00:00:00 /bin/ksh ./OSWatcherFM.sh 168 4root 109348 59019 0 03:37 pts/1 00:00:00 grep OSW

For more details about oswatcher, refer to the following official documentation (Note: currently, article 1585389.1 records how to permanently modify the osw settings on exadata, but during my testing, this document does not have relevant records)

OSWatcher does not Retain Data for the Full Retention Period Specified (Doc ID 1585389.1)

OSWatcher Black Box (DES: [Video]) (Doc ID 301137.1)

This article from the "Little Dog nest" blog, please be sure to keep this source http://hsbxxl.blog.51cto.com/181620/1354316