IBM E027SLL-H Troubleshooting Guide - Page 51

Procedure

Get IBM E027SLL-H - Tivoli Monitoring - PC PDF manuals and user guides View all IBM E027SLL-H manuals
Add to My Manuals
Save this manual to your list of manuals

Page 51 highlights

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 UTSNAME, SUM(BYTES) FREEBYTES FROM SYS.DBA_FREE_SPACE GROUP BY TABLESPACE_NAME; Enabled: Set FREEBYTES to zero Navigation Tree : Databases->Database Summary Chapter 3. Common problem solving 33

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
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
UTSNAME,
SUM(BYTES)
FREEBYTES
FROM
SYS.DBA_FREE_SPACE
GROUP BY TABLESPACE_NAME;
Enabled: Set FREEBYTES to zero
Navigation Tree : Databases->Database Summary
Chapter 3. Common problem solving
33