Search results for query: *

Has anyone clustered TEC? If so what clustering software have you used and what key issues did you run into? thanks...

I don't know that error. I would send it and your wtdbspace output to Tivoli support (TEC support level II)...sorry

Yes, you want to turn on rim tracing on your T/EC server: setup a rim trace: 1. wrimtrace tec "ERROR | INFORMATION" 2. kill all RIM processes 3. then lookup trace in /tmp/rim_db_log to turn it off: 4. wrimtrace tec "TRACE_OFF"

Very interesting. Thanks for the response. I haven't seen the volume of lockup issues with this since we loaded fixpack 1 (FP01). Your approach is very interesting to me though, since there are people here starting to talk about linux.

All users experience this problem. The tec 3.8 java console will "freeze" and need to be killed and restarted fairly often. In an 8 hour shift, technicians may need to restart their TEC 20+ times. Anybody else have this problem?

we had the same problems. After working through the problem with Tivoli, we eventually just used the dbassist to generate the scripts, then we gave the scripts to our dba. Our dba looked at them and said they needed to be customized to work and he re-wrote them. We then ran his re-written...

We found out we needed to create a target and apply it to the rulepack. It is in the 3.8 rule builders guide on page 37, but it is sort of buried. Once we created and applied the target, events hit the rulebase: wrb -crttarget EventServer -import tgtpack TGT

We upgraded TEC from 3.62 to 3.8. The classes and rules import fine and wrb -comprules -trace RB works without failing. However, no events go through the rulebase. They do, however, hit the event consoles. wlsesvrcfg -t Trace rule execution: Yes Rule trace output file: /tmp/rules.trace wrb...