IBM E027SLL-H - Tivoli Monitoring - PC Troubleshooting Manual page 51

Troubleshooting guide
Table of Contents

Advertisement

Procedure
Corrective actions
1. Disable the problematic cursors by setting an environment variable:
v
COLL_DISABLE_CURSORS
a. Launch Manage Tivoli Enterprise Monitoring Services.
b. Right-click the row that contains the name of the monitoring agent whose
environment variables you want to set.
c. From the pop-up menu, select Advanced > Edit Variables.
d. If the agent is running, accept the prompt to stop the agent.
e. The list dialog box is displayed. When only the default settings are in
effect, variables are not displayed. The variables are listed after you
override them. Override the variable settings:
1) Click Add.
2) From the Variable menu, select COLL_DISABLE_CURSORS. If the variable
is not there, you can add it.
3) In the Value field, type a value and click OK twice.
4) Restart the agent.
v
db_extparms
a. Use a text editor to enter a new value for the db_extparms in the
hostname_or_instance_name.cfg file in the install_dir/config directory.
b. The cursors that are listed below take longer to return data and consume
excessive system resources in some customer environments: DB3, DB6,
KF1, KF4, STATLTRN, TS1, TS3, TS5, , and TS6.
c. Each comma-delimited, no white space, value represents a change to the
SQL cursor that is executed during data gathering operations within the
agent. The values are the SQL cursor name. For example, setting the
Extended Parameters field to DB3, TS1 means that the DB3 and TS1 SQL
cursor is enabled for Set FREEBYTES to zero, Set TSNEXTS to zero, and
Set MAXEXTTS to zero. The SQL cursor name is not case sensitive.
2. Recycle the Monitoring Agent for Oracle to recognize these changes to the
Extended Parameters value.
3. Using the name of the SQL cursor, you can look in the korcoll.ctl file for the
SQL modification that is done when the SQL cursor is enabled. The
korcoll.ctl file is located in the following locations:
v
%CANDLE_HOME%\TMAITM6
v
$CANDLEHOME/misc
When these cursors are enabled, the Monitoring Agent for Oracle displays
default attribute values of these cursors in the Tivoli Enterprise Portal,
meaning, the Monitoring Agent for Oracle no longer monitors the attributes of
the enabled cursors.
4. An example of an SQL cursor is displayed below:
SQL cursor: DB3 - ARCHIVE LOG DISPLAY
SQL:
SELECT TABLESPACE_NAME
SUM(BYTES)
FROM
SYS.DBA_FREE_SPACE
GROUP BY TABLESPACE_NAME;
Enabled: Set FREEBYTES to zero
Navigation Tree : Databases->Database Summary
UTSNAME,
FREEBYTES
Chapter 3. Common problem solving
33

Advertisement

Table of Contents
loading

This manual is also suitable for:

Tivoli monitoring 6.2.3 fp1

Table of Contents