IBM Support

Maintaining NetView databases

Technote (FAQ)


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 no 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.

Cross reference information
Segment Product Component Platform Version Edition
Systems Management and Tivoli Tivoli NetView NetView AIX, Solaris 6.x, 7.x

Document information

More support for: Tivoli NetView

Software version: 7.1.x, 7.1.4, 7.1.5

Operating system(s): AIX, Linux, Solaris

Reference #: 1049488

Modified date: 23 January 2014