If ovtopmd is coring, then there has been some corruption in your database that
he cannot deal with and every time he reads it he cores.  If restoring from a
backup doesn't help, then you can only do one of three things.   Did you
increase
the size of .usr because you previously filled up?  If so, then that is probably
how things got messed up.
(1) try running the database utilities such as ovtopofix -a  and see if that
helps.
(2) obtain 5.1.3 and install that  since the core you are seeing may be fixed at
a later level and you are quite behind
(3) clear you databases (limited) and start over re-discovering your network

No matter which option you choose, you might want to call Support and get some
help.

James Shanks
Tivoli (NetView for UNIX and NT) L3 Support


Vassila Natassa <natasa AT nbg DOT gr> on 05/26/2000 09:00:49 AM

Please respond to IBM NetView Discussion <nv-l AT tkg DOT com>

To:   "'Discussion of IBM NetView and POLYCENTER Manager on NetView' (E-mail)"
      <NV-L AT tkg DOT com>
cc:    (bcc: James Shanks/Tivoli Systems)
Subject:  [NV-L] ovtopmd won't start




Hello everyone,
After a rather unexpected power-off of the NV server, the ovtopmd
daemon won't start. It exits  on signal 11 (segmentation violation)
and core dumps.
I have run out of ideas how to overcome this problem...
I have restored a previous system backup with no luck, I have even
increased the size of the /usr filesystem. Has anyone come by the same
problem??
Any help will be highly appreciated as all I can think of is reinstall NV...

System info: AIX 4.3.2, NetView v5.1.1

Cheers,


Natascha Vassila
National Bank of Greece


_________________________________________________________________________

NV-L List information (unsubscribing, policies, posting, digest version,
searchable archives): http://www.tkg.com/nv-l