here to order the book online!
Administer Oracle9i on all of the major UNIX platforms, including Solaris,
HP-UNIX and IBM-UNIX, and Linux.
Descriptions of useful Oracle scripts from Oracle9i UNIX Administration
Handbook by Oracle Press.
This is a collection if references to useful scripts that can be found in the
Oracle9i UNIX Administration Handbook, (c) 2002 by Oracle Press.
Capturing vmstat data inside Oracle
It is a simple matter to create an Oracle table to store
this information and use a script to populate the table. Creating the automated
vmstat monitor begins by creating an Oracle table to
Now that we have defined an Oracle table to capture the
vmstat information, we need to write a UNIX script that will execute
vmstat, capture the vmstat output, and place it into the Oracle table.
The main script to collect the vmstat information is a
Korn shell script called get_vmstat.ksh. As we noted earlier, each
dialect of UNIX displays vmstat information in different columns, so we need
slightly different scripts for each type of UNIX.
The idea is to write a script that continually runs the vmstat utility and then
directs the results into our Oracle table.
To get a complete picture of the performance of your
total Oracle system, you must also monitor the behavior of all of the servers
that communicate with Oracle. For example, many Oracle environments have other
Oracle Applications In Oracle Applications products, you
generally have separate application servers communicating with the database
SAP with Oracle In SAP, you have separate application
servers that communicate with Oracle.
Real Application Clusters (Oracle Parallel Server) With
RAC, you have multiple Oracle database servers, all sharing the same database.
Oracle Web Applications When using Oracle databases on the
Web, you have separate WebServers that direct the communications into the
This technique in get_vmstat.ksh can easily be extended to measure the
performance of other servers in your Oracle environment. Note that the
stats$vmstat table has a column to store the server name. Since we can separate
vmstat metrics by server, we simply need to create a remote vmstat script that
will capture the performance of the other servers and send the data to a central
database. Because only the database server contains an Oracle database, the
vmstat data will be sent to the database from the remote server using database
Any server that has a Net8 client can be used to capture
To get details on this technique,
Click here to order the book online!