What NetView daemons and processes must be stopped before running NetView databases maintenance?
NetView databases maintenance needs to be run periodically to maintain data consistency across the object, topology and map databases. The maintenance frequency is influenced by the number of objects being managed, and the number of changes (add/delete/modify) made to the map(s).
NetView database maintenance usually consists of 2 steps. The first is "/usr/OV/bin/ovmapcount -a". For this step, all NetView daemons can be up, make sure that no NetView GUIs are running. This includes the native NetView GUI, ovw, and any web client GUIs.
The second step is "/usr/OV/bin/ovtopofix -a". For this step, the NetView GUIs can be up, but any changes should be made to the map while ovtopofix is running. To be on the safe side, it is a good idea (but not required) to stop all NetView GUIs. The NetView daemon, netmon, must be stopped prior to running ovtopofix. This is accomplished by running "/usr/OV/bin/ovstop netmon". All other NetView daemons can remain active.
|Systems Management and Tivoli||Tivoli NetView||NetView||AIX, Solaris||6.x, 7.x|
Rate this page:
Copyright and trademark information
IBM, the IBM logo and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.