IBM E027SLL-H Troubleshooting Guide - Page 67

KBB_RAS1=ERROR UNIT:ksysql1 ALL

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

KBB_RAS1=ERROR (UNIT:ksy4 ALL) ResultSet level trace for summarization. Affects the content of the Java-based internal tracing (hostname_sy_java_timestamp-n.log). KBB_RAS1=ERROR (UNIT:ksy5 ALL) Column value level trace for summarization. Affects the content of the Java-based internal tracing (hostname_sy_java_timestamp-n.log). KBB_RAS1=ERROR (UNIT:ksysql ALL) Traces every SQL statement being executed. Affects the content of the Java-based internal tracing (hostname_sy_java_timestamp-n.log). KBB_RAS1=ERROR (UNIT:ksysql1 ALL) Same as (UNIT:ksysql ALL) but also includes all the parameter values used in the parameterized statements. Note: 1. The following settings: (UNIT:ksy3 ALL) or (UNIT:ksy4 ALL) or (UNIT:ksy5 ALL) produce a high volume of trace output. 2. By default, the Java-based internal trace (hostname_sy_java_timestamp-n.log) wraps at 5 files, and each file contains 300000 lines. To change the defaults, use the following settings in the KSYENV (Windows) or sy.ini (UNIX) files: KSZ_JAVA_ARGS=-Dibm.tdw.maxNumberDetailTraceFiles= -Dibm.tdw.maxLinesForDetailTraceFile= where: Specifies the maximum number of Java-based internal trace files that can exist at any one time for a single launch Specifies the maximum number of lines per Java-based internal trace file. Using the Summarization and Pruning Agent user interface: You can edit the handler configuration file $CANDLEHOME%\Config\ ITMConfigRAS.properties for UNIX systems and the %CANDLEHOME%\Config\ ITMConfigRAS.properties file for Windows systems, and set the handler99 as the configuration handler and set the debug tracing to the maximum DEBUG_MAX as shown below: Handler99.name=config Handler99.scope=* Handler99.scopeName=Config Handler99.logFile=../logs/config.log Handler99.traceFile=../logs/config.trc Handler99.level=DEBUG_MAX Handler99.onConsoleToo=true Handler99.maxFiles=10 Handler99.maxFileSize=8192 Then you need to create a file called kKSYconfig.sysprops.cfg under the directory $CANDLEHOME\TMAITM6 for UNIX systems, and %CANDLEHOME%\ TMAITM6 for Windows systems, containing a link to the handler configuration file as shown below: DInstallRASConfig="ITMConfigRAS.properties" When the Summarization and Pruning Agent configuration panel is executed, tracing appears in the $CANDLEHOME/logs/config.trc file for UNIX systems, and %CANDLEHOME%/logs/config.trc for Windows systems, as described by the handler configuration file. Chapter 4. Tools 49

  • 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
KBB_RAS1=ERROR (UNIT:ksy4 ALL)
ResultSet level trace for summarization. Affects the content of the
Java-based internal tracing (
hostname_sy_java_timestamp-n.log
).
KBB_RAS1=ERROR (UNIT:ksy5 ALL)
Column value level trace for summarization. Affects the content of the
Java-based internal tracing (
hostname_sy_java_timestamp-n.log
).
KBB_RAS1=ERROR (UNIT:ksysql ALL)
Traces every SQL statement being executed. Affects the content of the
Java-based internal tracing (
hostname_sy_java_timestamp-n.log
).
KBB_RAS1=ERROR (UNIT:ksysql1 ALL)
Same as (UNIT:ksysql ALL) but also includes all the parameter values used
in the parameterized statements.
Note:
1.
The following settings: (UNIT:ksy3 ALL) or (UNIT:ksy4 ALL) or (UNIT:ksy5
ALL) produce a high volume of trace output.
2.
By default, the Java-based internal trace (
hostname_sy_java_timestamp-n.log
)
wraps at 5 files, and each file contains 300000 lines. To change the defaults, use
the following settings in the
KSYENV
(Windows) or
sy.ini
(UNIX) files:
KSZ_JAVA_ARGS=-Dibm.tdw.maxNumberDetailTraceFiles=<A>
-Dibm.tdw.maxLinesForDetailTraceFile=<B>
where:
<A>
Specifies the maximum number of Java-based internal trace files that
can exist at any one time for a single launch
<B>
Specifies the maximum number of lines per Java-based internal trace
file.
Using the Summarization and Pruning Agent user interface:
You can edit the handler configuration file
$CANDLEHOME%\Config\
ITMConfigRAS.properties
for UNIX systems and the
%CANDLEHOME%\Config\
ITMConfigRAS.properties
file for Windows systems, and set the handler99 as the
configuration handler and set the debug tracing to the maximum DEBUG_MAX as
shown below:
Handler99.name=config
Handler99.scope=*
Handler99.scopeName=Config
Handler99.logFile=../logs/config.log
Handler99.traceFile=../logs/config.trc
Handler99.level=DEBUG_MAX
Handler99.onConsoleToo=true
Handler99.maxFiles=10
Handler99.maxFileSize=8192
Then you need to create a file called
kKSYconfig.sysprops.cfg
under the directory
$CANDLEHOME\TMAITM6 for UNIX systems, and %CANDLEHOME%\
TMAITM6 for Windows systems, containing a link to the handler configuration file
as shown below:
DInstallRASConfig="ITMConfigRAS.properties"
When the Summarization and Pruning Agent configuration panel is executed,
tracing appears in the
$CANDLEHOME/logs/config.trc
file for UNIX systems, and
%CANDLEHOME%/logs/config.trc
for Windows systems, as described by the handler
configuration file.
Chapter 4. Tools
49