IBM E027SLL-H Troubleshooting Guide - Page 206

Summarization and Pruning Agent

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

Unable to receive summarized data for the last hour in the Tivoli Enterprise Portal The Summarization and Pruning Agent does not run continuously. It is scheduled to run at some frequency or on a fixed schedule. Data for the last hour likely will not be available until this agent has just finished running and has had enough data to compute the last hour summary, which a data sample exists for the following hour. The Summarization and Pruning Agent does not summarize hour X until at least one sample for hour X+1 is available in the Tivoli Data Warehouse at the time the summarization is started for that agent. Summarization for CCC logs is not allowed You cannot set summarization for CCC logs. If summarization is set up for CCC logs, it can be undone again using the command-line interface. Receive errors when modifying the JAVA HEAP SIZE for the Summarization and Pruning Agent On 32-bit Windows systems with 4 GB of RAM, there is a maximum heap-size limit of approximately 1.6 GB. You might need to add the /3GB switch to the boot.ini file. Determine the max heap size in MBs by testing when setting KSZ_JAVA_ARGS=-Xms256M -XmxSIZEM in the KSYENV file. If the -Xmx value is too large, the agent fails with an error. When associating situations, they fire, but cannot be viewed When a situation association is done at a specific node level on the navigator tree, the situation fires when true, and the event is then associated to the navigator item. The situation is not associated with that navigator item if the navigator item or node is not part of its distribution. The Summarization and Pruning agent fails when processing an index created in a previous release of the product About this task If a database insert fails while running the Summarization and Pruning Agent, and the message indicates the insert has failed because the maximum index size has been exceeded, complete the following steps to correct this issue: 1. Stop the Summarization and Pruning Agent. 2. Drop the index causing the failure. 3. Run the Schema Publication Tool in configured mode: KSY_PRODUCT_SELECT = configured 4. Open the tdw_schema_index.sql file and find the index that was deleted in step 1. 5. Edit out all statements except the index you want to recreate. 6. Run the create index statement. 7. Start the Summarization and Pruning Agent. 188 IBM Tivoli Monitoring: Troubleshooting Guide

  • 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
Unable to receive summarized data for the last hour in the Tivoli
Enterprise Portal
The Summarization and Pruning Agent does not run continuously. It is scheduled
to run at some frequency or on a fixed schedule. Data for the last hour likely will
not be available until this agent has just finished running and has had enough data
to compute the last hour summary, which a data sample exists for the following
hour.
The Summarization and Pruning Agent does not summarize hour
X
until at least
one sample for hour
X
+1 is available in the Tivoli Data Warehouse at the time the
summarization is started for that agent.
Summarization for CCC logs is not allowed
You cannot set summarization for CCC logs. If summarization is set up for CCC
logs, it can be undone again using the command-line interface.
Receive errors when modifying the JAVA HEAP SIZE for the
Summarization and Pruning Agent
On 32-bit Windows systems with 4 GB of RAM, there is a maximum heap-size
limit of approximately 1.6 GB. You might need to add the /3GB switch to the
boot.ini
file. Determine the max heap size in MBs by testing when setting
KSZ_JAVA_ARGS=-Xms256M -XmxSIZEM in the
KSYENV
file. If the -Xmx value is
too large, the agent fails with an error.
When associating situations, they fire, but cannot be viewed
When a situation association is done at a specific node level on the navigator tree,
the situation fires when true, and the event is then associated to the navigator
item. The situation is not associated with that navigator item if the navigator item
or node is not part of its distribution.
The Summarization and Pruning agent fails when processing an index
created in a previous release of the product
About this task
If a database insert fails while running the Summarization and Pruning Agent, and
the message indicates the insert has failed because the maximum index size has
been exceeded, complete the following steps to correct this issue:
1.
Stop the Summarization and Pruning Agent.
2.
Drop the index causing the failure.
3.
Run the Schema Publication Tool in configured mode:
KSY_PRODUCT_SELECT = configured
4.
Open the
tdw_schema_index.sql
file and find the index that was deleted in step
1.
5.
Edit out all statements except the index you want to recreate.
6.
Run the create index statement.
7.
Start the Summarization and Pruning Agent.
188
IBM Tivoli Monitoring: Troubleshooting Guide