IBM E027SLL-H Troubleshooting Guide - Page 43

server attribute groups

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

What to do next For more information about the persistent data store, see the IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/OS: Common Planning and Configuration Guide. Historical data does not get collected for some monitoring server attribute groups Problem Description: When configuring ITM Historical Data Collection, the following attribute groups can not successfully be stored at the agent when an agent runs on the z/OS platform. CCC Logs - Agent Operations Log CCC Logs ITM Audit This is a limitation in the current implementation of ITM history collection for these attribute groups that should be fixed in a future release. The following error messages will be visible in the z/OS agent RAS1 log (RKLVLOG) when this problem occurs (time stamp not shown): (0034-D8CDE7B3:kraahbin.cpp,977,"ConnectToPDS") Unable to locate table KRAAUDIT (0034-D8CDE7B3:kraahbin.cpp,977,"ConnectToPDS") Unable to locate table OPLOG When historical collection data is required from any z/OS monitoring agent for the CCC Logs - Agent Operations Log or CCC Logs - ITM Audit attribute groups, configure Historical Data Collection for short-term data storage at the TEMS rather than at the agent. A situation does not raise when expected You can encounter a problem that a situation does not raise. For example, certain conditions may not raise a situation as expected. Symptoms of the problem: v In the portal client or Tivoli Enterprise Console, certain conditions exist that should have raised a situation but the situation has not been raised. Diagnosing that a situation does not raise when expected You can diagnose that a situation does not open an event when expected by verifying that the monitoring agent has started. About this task To diagnose that a situation does not raise when expected, perform the following steps: Procedure Preliminary diagnostics 1. Verify that the monitoring agent has started. 2. Verify that the situation is associated with a Navigator item in the Tivoli Enterprise Portal. 3. In the situation event console, confirm that the situation is true and an event has opened. 4. Verify that maintenance has not been run against situations. One possible tacmd command that could have been run is the tacmd maintAgent. If maintenance has been run, wait for the situation to restart. Chapter 3. Common problem solving 25

  • 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
What to do next
For more information about the persistent data store, see the
IBM Tivoli
OMEGAMON XE and Tivoli Management Services on z/OS: Common Planning and
Configuration Guide
.
Historical data does not get collected for some monitoring
server attribute groups
Problem Description: When configuring ITM Historical Data Collection, the
following attribute groups can not successfully be stored at the agent when an
agent runs on the z/OS platform. CCC Logs - Agent Operations Log CCC Logs -
ITM Audit This is a limitation in the current implementation of ITM history
collection for these attribute groups that should be fixed in a future release.
The following error messages will be visible in the z/OS agent RAS1 log
(RKLVLOG) when this problem occurs (time stamp not shown):
(0034-D8CDE7B3:kraahbin.cpp,977,"ConnectToPDS") Unable to locate table KRAAUDIT
(0034-D8CDE7B3:kraahbin.cpp,977,"ConnectToPDS") Unable to locate table OPLOG
When historical collection data is required from any z/OS monitoring agent for the
CCC Logs - Agent Operations Log or CCC Logs - ITM Audit attribute groups,
configure Historical Data Collection for short-term data storage at the TEMS rather
than at the agent.
A situation does not raise when expected
You can encounter a problem that a situation does not raise. For example, certain
conditions may not raise a situation as expected.
Symptoms of the problem:
v
In the portal client or Tivoli Enterprise Console, certain conditions exist that
should have raised a situation but the situation has not been raised.
Diagnosing that a situation does not raise when expected
You can diagnose that a situation does not open an event when expected by
verifying that the monitoring agent has started.
About this task
To diagnose that a situation does not raise when expected, perform the following
steps:
Procedure
Preliminary diagnostics
1.
Verify that the monitoring agent has started.
2.
Verify that the situation is associated with a Navigator item in the Tivoli
Enterprise Portal.
3.
In the situation event console, confirm that the situation is true and an event
has opened.
4.
Verify that maintenance has not been run against situations. One possible
tacmd command that could have been run is the
tacmd maintAgent
. If
maintenance has been run, wait for the situation to restart.
Chapter 3. Common problem solving
25