Hi James, many thanks for your response. I believe the high CPU started
occurring when 'MANUAL' changes were made to map.  I will give your
suggestions a go.  Thanks again.

-----Original Message-----
From: owner-nv-l AT lists.us.ibm DOT com [mailto:owner-nv-l AT lists.us.ibm DOT 
com]
On Behalf Of James Shanks
Sent: 05 April 2006 14:22
To: nv-l AT lists.us.ibm DOT com
Subject: Re: [nv-l] Netview 7.1.4 - High CPU - ovtopmd

ovtopmd is the access to the topology database, which has to be in synch
with the object database, owned by ovwdb. Usually it is netmon who makes
this happen, but if you've had problems with netmon failing, or you've
done
any manual map changes, they can get out of synch.
I would ovstop netmon and ovtopmd and run ovtopofix, and check the
output
for anomalies.  Check the man page on ovtopofix to see what options are
appropriate for your environment, but generally it is -A or -a,
depending
on how many maps you have.

James Shanks
Level 3 Support  for Tivoli NetView for UNIX and Windows
Tivoli Software / IBM Software Group


 

             "Paul Campbell"

             <[email protected]

             et.uk>
To 
             Sent by:                  <nv-l AT lists.tivoli DOT com>

             owner-nv-l@lists.
cc 
             us.ibm.com

 
Subject 
                                       [nv-l] Netview 7.1.4 - High CPU -

             04/05/2006 04:30          ovtopmd

             AM

 

 

             Please respond to

             nv-l AT lists.us DOT ibm

                   .com

 

 






Hi List,

Can anyone point me in the direction in determining why the process
ovtopmd
is causing our system to run 100% CPU?  We are running Netview. 7.1.4,
Fixpack 3 on Solaris 9.

Thanks in advanced.

Paul Campbell
Engineering Specialist
Managed Technology Services

E  - pcampbell AT star.net DOT uk
DDI +44 (0) 1285 880067
M  - +44 (0) 7795 605472
W  - www.star.net.uk

Company Registration No - 3077786




______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________




______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________