IBM E027SLL-H Troubleshooting Guide - Page 191

Warehouse agents

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 191 highlights

is used in a system command in the Situation editor's Action tab, the raw data from the agent is substituted. For example, if a situation had an action command to send an email, it could look like this in the Situation editor: my_command Warning too many processes &{System.Load_Average_1_Min} options If the average was actually 6.99 as displayed in the portal client, the command would be executed as: my_command Warning too many processes 699 options Using &{xx.yy} is the best way to specify an attribute because there is no uncertainty about what attribute is being used. It allows adding characters to the command without spaces, such as a forward slash (/) or backward slash (\). IBM Tivoli Monitoring V6.2.2 FP6 IZ98638 does not support reflex actions for OMEGAMON XE agents on z/OS You might encounter a problem using reflex actions for your OMEGAMON XE agents on z/OS. Note that IBM Tivoli Monitoring V6.2.2 FP6 IZ98638 does not support reflex actions for OMEGAMON XE agents on z/OS. Take action command names do not accept non-English characters There is not a workaround at the present time. Warehouse agents Review the warehouse proxy agent and summarization and pruning agent topics for help with configuration and usage problems. Configuring the Summarization and Pruning Agent with an incorrect JDBC driver JAR file If you add an incorrect JDBC driver JAR file when configuring the Summarization and Pruning Agent, an error message is displayed after you click Test Connection. The error message continues to display, even after you have replaced the file with the correct one. This behavior is a known limitation. Close the configuration panel and run the configuration again. Memory leak on Solaris OS during khdxprtj process causes applications to hang The Oracle JDBC driver version V10.2.0.3.0 causes an application to hang when it tries to acquire a connection to the database. The most common symptoms affecting the Summarization and Pruning agent or Warehouse Proxy Agent are: v lack of Tivoli Enterprise Portal responsiveness v agent upload failures for Warehouse Proxy Agent v increased memory usage over time v rejecting a shutdown command To resolve this issue, upgrade the JDBC driver to a newer level (at least V10.2.0.5.0 or later). Chapter 10. Monitoring agent troubleshooting 173

  • 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
is used in a system command in the Situation editor's
Action
tab, the raw data
from the agent is substituted. For example, if a situation had an action command
to send an email, it could look like this in the Situation editor:
my_command Warning too many processes &{System.Load_Average_1_Min} options
If the average was actually 6.99 as displayed in the portal client, the command
would be executed as:
my_command Warning too many processes 699 options
Using
&{xx.yy}
is the best way to specify an attribute because there is no
uncertainty about what attribute is being used. It allows adding characters to the
command without spaces, such as a forward slash (/) or backward slash (\).
IBM Tivoli Monitoring V6.2.2 FP6 IZ98638 does not support reflex
actions for OMEGAMON XE agents on z/OS
You might encounter a problem using reflex actions for your OMEGAMON XE
agents on z/OS. Note that IBM Tivoli Monitoring V6.2.2 FP6 IZ98638 does not
support reflex actions for OMEGAMON XE agents on z/OS.
Take action command names do not accept non-English
characters
There is not a workaround at the present time.
Warehouse agents
Review the warehouse proxy agent and summarization and pruning agent topics
for help with configuration and usage problems.
Configuring the Summarization and Pruning Agent with an
incorrect JDBC driver JAR file
If you add an incorrect JDBC driver JAR file when configuring the Summarization
and Pruning Agent, an error message is displayed after you click Test Connection.
The error message continues to display, even after you have replaced the file with
the correct one. This behavior is a known limitation. Close the configuration panel
and run the configuration again.
Memory leak on Solaris OS during khdxprtj process causes
applications to hang
The Oracle JDBC driver version V10.2.0.3.0 causes an application to hang when it
tries to acquire a connection to the database. The most common symptoms
affecting the Summarization and Pruning agent or Warehouse Proxy Agent are:
v
lack of Tivoli Enterprise Portal responsiveness
v
agent upload failures for Warehouse Proxy Agent
v
increased memory usage over time
v
rejecting a shutdown command
To resolve this issue, upgrade the JDBC driver to a newer level (at least V10.2.0.5.0
or later).
Chapter 10. Monitoring agent troubleshooting
173