Scott,
I actually also has some problems with tecad_nv6k. It
was using up about 100% of the processor at all time,
I played around with it for a month before I decided
to just backup the usr\ov\databases \conf directories,
uninstall, reinstall, and restore the old db and conf
files. It seems to have fixed the problem for me.
It wasn't a consistent problem for me, it can works
for weeks once it actually loads correctly, but once I
shut it done and bring it backup, it would not come up
all the time. Because the box was not complete in my
control, server support people may have install
patches, new service pack, etc. I thought some .DLL
might have gotten registered incorrectly in NT, which
troubleshooting is like looking for a needle in a
haystack.
If you have the luxury to taking the box down for a
half day, backup, Uninstall and reinstall (not just
reinstall). It should just fix the problem.
Xu
--- James_Shanks AT tivoli DOT com wrote:
>
>
> I'd say you need to re-open your problem with Tivoli
> and get them to look more
> closely at the Dr. Watson's you are having.
> We have no known Dr. Watson issues with the old,
> that is 5.1.3, tecad_nv6k.exe,
> reported. It has been running in our Verification
> labs for months. I tested it
> a few times myself. I have not run it on a V6 box
> however. We would not
> normally do that.
>
> As far as V6 goes, that was a different story. If
> you are running V6 and have
> problems, then Tivoli Support should be able to
> provide you with a copy of the
> one that will be shipped in 6.0.1. Fixes were made
> to the 6.0 code and the
> resulting new one has been blessed by Verification
> and by some other customers
> already.
>
> In general, you usually cannot solve Dr. Watson's by
> yourself. They represent
> unforeseen events that the code cannot handle. Once
> in a while you might be
> able to avoid them by not doing something, so that
> the unexpected condition does
> not occur, but in this case, probably not. My guess
> is that some trap comes
> through to be forwarded and the config you have set
> up causes some part of the
> code to be executed you have no control over. You
> could try looking at the log
> and the event browser and see if you can determine
> what trap that is and then
> changing your config to avoid it, but that's about
> all. But that's just a
> guess. No one can debug your problem with looking
> at your logs and traces and
> the Dr. Watson.
>
>
>
> James Shanks
> Team Leader, Level 3 Support
> Tivoli NetView for UNIX and NT
>
>
>
> "richard.b.odom" <richard.b.odom AT us.army DOT mil> on
> 07/24/2000 04:56:31 PM
>
> Please respond to IBM NetView Discussion
> <nv-l AT tkg DOT com>
>
> To: nv-l AT tkg DOT com
> cc: scottbb AT earthlink DOT net (bcc: James
> Shanks/Tivoli Systems)
> Subject: [NV-L] NT and Tecad
>
>
>
>
> We have been trying to get the tecad daemon to come
> up and stay up on NT
> since we got the product. Neither the 5.x or 6.0
> versions of non-TME or
> TME seem to stay up.
>
> Right now we are running version 6 of NetView and
> the 5.x non-TME tecad
> daemon. It won't even come up unless we do logging
> on low diskspace. Dr.
> Watson and tecad have become good friends.
>
> We've contacted Tivoli before and that's how we
> ended up on tecad 5 and
> NetView 6. If anyone has information on how to
> stablize tecad in an NT
> environment--we'd sure appreciate it.
>
>
_________________________________________________________________________
> NV-L List information and Archives:
> http://www.tkg.com/nv-l
>
>
>
>
_________________________________________________________________________
> NV-L List information and Archives:
http://www.tkg.com/nv-l
=====
Xu He
Consulting Services Engineer
Network Solutions, Inc
http://www.netsol.com/consulting
__________________________________________________
Do You Yahoo!?
|
