Usage |
Command line |
Called without any parameter, sreport.sh displays a short help
page concerning its command line parameters. A normal, successful run can
be done with just passing it the ORACLE_SID of the instance to
report on as only parameter – provided your Oracle environment is set up to
support a connect with the syntax "CONNECT user/password@ORACLE_SID ".
More command line parameters are available and listed in the table below:
|
Parameter | Description |
-b |
BEGIN_SNAP_ID and
END_SNAP_ID for the report. See
configuration section on
START_ID and END_ID for details. |
-e |
-c |
alternative configuration file to use. You may create
different configurations according to e.g. special cases (such
as e.g. running a complete report containing all blocks just once
a week, while having a shorter everyday report), or for groups of
instances you want to monitor the same blocks or having the same
user/password combinations in, and then just specify the corresponding
config file at the command line. This file must be executable by the
user running the report. |
-u |
User name (-u ) and password
(-p ) for the SQL CONNECT statement. Although
you may specify it here, this is not recommended for security reasons.
Better configure it in the configuration
file. |
-p |
-o |
Use alternative output file name (where the HTML output
shall be written to) |
-r |
Use alternative report directory (where the HTML output
shall be written to) |
-s |
Connection string for the SQL CONNECT
statement (if different from the ORACLE_SID ). This
is used for the SQL CONNECT string only, while the
ORACLE_SID is also used for the report's file name. |
|
An example command line could look like this:
./sreport.sh oradb -c diagnostic.config -b 1521 -e 1712 -o special.html
|
|
fts_plans.sh |
For the fts_plans.sh script, the same command line syntax applies.
You may want to use this script, if you have many data file sequential
reads , and the "Wait Objects" segments of OSPRep's report indicates that
this is because of too many full table scans (FTS). fts_plans.sh
retrieves the latest execution plans for all statements that caused full table
scans (i.e., if the latest execution plan indicates FTS) for the given interval.
If your database already has a long uptime, you may be forced to specify a
snapshot range (this is due to a limitation in PL/SQL: the dbms_output
package is limited to 1000000 chars). In this case, specify the END_ID
taken from the report's "SnapShot Info" block, and specify a BEGIN_ID
that is between "END_ID -1" and "END_ID -120" (i.e.
up to 5 days in the past) -- depending on your database size and traffic you
may have to experiment a bit with those values. Of course, these are only guiding
values - there may be cases to specify an BEGIN_ID that is earlier
than 5 days before the START_ID -- I leave this choice up to you :-)
|
charts.sh |
Use this script to create charts for selected statistics. It has the same
command line syntax as the other scripts, and creates its pages in the
configured REPDIR , using the file name <ORACLE_SID>_chart.html .
The charts themselves are created via JavaScript - so there are no additional
requirements like a graphics engine. Only your browser has to support JavaScript,
which most browsers will. I tested it with M$IE and Mozilla Firefox in Windows,
plus with Mozilla in Linux.
|