Oracle OSW Installation

Production environment highly recommended installation deployment
Introduction

Oswatcher (OSWBB) is a collection of UNIX shells scripts intended to collect and archive operating system and network Metri CS to aid support in diagnosing performance issues. As a best practice, the all customers should install and run Oswatcher on every node, have a running Oracle instance. In the case of a performance issue, Oracle support can use this data to help diagnose performance problems which may Outsi De the database. Oswatcher can downloaded from MOS Note 301137.1. Installation instructions for Oswatcher is provided in the This User guide.

See documentation for specific installation procedures, 301137.1

Installationthe following sections describe how to install and remove oswatcher on your system. Installing Oswbboswatcher can is installed as any user as long as that user have permission to execute the underlying Unix Utilities such as Vmstat, top, etc. Cases you can install as the Oracle user. Oswatcher needs to is installed on each node if you is running in a RAC environment, one installation per node. Install by using the following procedure:downloaded the Oswbb.tar file from MOS. Place the tar file is the desired locatio N and Untar the file. Next, make sure to change the file permissions in these files to execute by using Chmod.tar xvf oswbb.tarchmod 744 *a Dire Ctory named Oswbb'll be created which contains the full installation of oswatcher including the Oswatcher Analyzer and a ll supporting files. Oswatcher is now installed. Uninstalling oswbbto Uninstall Oswatcher issue the following command on the OSWBB directory.rm-rf oswbbback to Contentsco Nfigurationoswatcher CollECTS and stores data to files in an archive directory. By default, this directory was created under the OSWBB directory where OSWBB is installed. There is 2 options if you want to the change this location to the point to any other directory or device.1. Set the UNIX environment variable oswbb_archive_dest to the location desired before starting the tool. In this example the archive directory would be created in this location (/usr/app/archive) and not created under the home O SWBB Directoryexport oswbb_archive_dest=/usr/app/archive2. Start OSWBB by running the startoswbb.sh script located in the directory where OSWBB is installed and specify the 4th para Meter on the command line. /STARTOSWBB None/usr/app/archivethis Script accepts an optional 4th parameter which are the location where you want OSWBB to write the data it collects. If You use the optional 4th parameter must also set the optional 3rd parameter which specifies the name of a compress or zip (gzip,compress, etc) utility.If you don't want to compress the files you can specify NONE as the 3rd parameter. See the startoswbb.sh for more details. OSWBB writes the archive location to a heartbeat file named OSW.HB in The/tmp directory. This is the so-utilities Oracle-like RAC-DDT and Ida can find OSWBB data when these utilities is run. This file gets removed when Oswatcher is stopped. Once OSWBB is installed, scripts has been provided to start and stop the OSWBB utility. When OSWBB was started for the first time it creates the archive subdirectory, either in the default location under the OSW BB directory or in a alternate location as specified above. The archive directory contains a minimum of 7 subdirectories, one for each data collector. Private networks can be monitored by using the traceroute command. This is the done automatically in release 8 of Oswatcher. This can also is done manually by the user by creating a executable file in the OSWBB directory named Private.net. An example of what the This file Should look like are named Exampleprivate.net with samples for each operating system:solaris, LINUX, AIX, and HP-UX in th e oswbb directory. This file can is edited and renamed Private.net or a new file named Private.net can be created. This is the file contains entries for running, the traceroute command to verify RAC private networks. Exampleprivate.net entry on Solaris:traceroute-r-F private_nodenamewhere node1 and Node2 is 2 nodes in addition to the Hostnode of a 3 node RAC cluster.  If The file private.net does not exist or isn't executable then no data would be collected and stored under the Oswprvtnet DIRECTORY.OSWBB would need access to the OS utilities:top, Vmstat, Iostat, Mpstat, Netstat, and traceroute.  These OS utilities need to is installed on the system prior to running OSWBB. Execute permission on these utilities need to being granted to the user of OSWBB. Contentsrac CONSIDERATIONSOSWBB needs to is installed on each node in the cluster. If installing on a shared file SystEm then install each node's OSWBB into a unique directory. Back to Contents

Oracle OSW Installation