不錯的工具,prw.sh

Applies to:

Purpose

Procwatcher is a tool to examine and monitor Oracle database and CRS processes at an interval. The tool will collect stack traces of these processes using Oracle tools like oradebug short_stack and OS debuggers like pstack, gdb, dbx, or ladebug.

Scope and Application

Procwatcher: Script to Monitor and Examine Oracle and CRS Processes

This script will find CRS and/or Oracle Background processes and collect stack traces for debugging. It will write a file called procname_pid_date.out for each process in its respective directory. If you are examining CRS then run this script as root. If you are only examining Oracle background processes then you can run as root or the oracle user.

To install the script, simply download it HERE, put it in its own directory, unzip it, and give it execute permissions.

Requirements:

- Must have /bin and /usr/bin in your $PATH
- Must have the relevant OS debugger installed on your platform. PRW looks for:

Linux - /usr/bin/gdb
HP-UX and HP Itanium - /opt/langtools/bin/gdb64
Sun - /usr/bin/pstack
IBM AIX - /bin/dbx
HP Tru64 - /bin/ladebug

- Recommended to set $ORACLE_HOME (PRW searches the oratab for the SID it finds and if it can't find the SID in the oratab it will default to $ORACLE_HOME).

Procwatcher Features:

- PRW collects stack traces for all processes defined using either oradebug short_stack or an OS debugger at a predefined interval.

- If USE_SQL is set to true, PRW will generate session wait, lock, and latch reports.

- If USE_SQL is set to true, PRW will look for wait events, lock, and latch contention and also dump stack traces of processes that are either waiting for non-idle wait events or waiting for or holding a lock or latch.

- If USE_SQL is set to true, PRW will dump session wait, lock, latch, and session history information into specific process files.

- You can define how aggressive PRW is about getting information by setting parameters like THROTTLE, IDLECPU, PROCINTERVAL, and INTERVAL. You can tune these parameters to either get the most information possible or to reduce PRW's cpu impact. See below for more information about what each of these parameters does.

- If CPU usage gets too high on the machine (as defined by IDLECPU), PRW will sleep and wait for CPU utilization to go down.

- PRW gets stack traces of ALL threads of a process.

- The housekeeper process runs on a 5 minute loop and cleans up files older than the specified number of days (default is 2).

- If USE_SQL is set to true and any SQL times out after 60 seconds it will be disabled. The housekeeper process (which is on a 5 minute loop), will re-enable SQL if the test passes.

- If oradebug shortstack is enabled and it times out, the housekeeper process will re-enable shortstack if the test passes.

To start Procwatcher (the 2nd argument is the # of days to keep files, default is 2):

To stop Procwatcher: :

To check the status of Procwatcher:

Sample directory structure:

Notice that it writes a log file for every day that it runs and creates a directory for CRS (PRW_CRS) and each DB that it finds (PRW_DB_$SID). The PRW_SYS directory contains files that prw uses at runtime (don't touch).

Sample log output:

Sample debug output:

Sample SQL Report (if USE_SQL=true):

Procwatcher Parameters:

Procwatcher also has some configurable parameters that can be set within the script itself. The script also provides more information on how to set each one. Here is the section of the script where parameters can be set:

For additional details, see the prw.sh script itself.