You can dump a nice list of the objects with
   ovobjprint -s > obj.list
This puts them in the order they were created in (object
id). It is sometimes useful to sort them on the selection
name, so you can see what objects are getting multiples
made for them.

Cordially,

Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
Detroit


                                                                                
          
                    "Barr, Scott"                                               
          
                    <Scott_Barr@csgsy       To:     "'IBM NetView Discussion'"  
          
                    stems.com>               <nv-l AT tkg DOT com>              
                 
                    Sent by:                cc:                                 
          
                    owner-nv-l AT tkg DOT co       Subject:     RE: [NV-L] 
ovwdb filling up with 
                    m                        objects                            
          
                                                                                
          
                                                                                
          
                    10/29/01 02:39 PM                                           
          
                    Please respond to                                           
          
                    IBM NetView                                                 
          
                    Discussion                                                  
          
                                                                                
          
                                                                                
          



We had a problem like this due to a device that NETMON was having trouble
during discovery. You said discovery isn't on, but if you are using a seed
file, then discovery is always running for things in your seed file.

The problem was a device on the network that had 4 async (re:ppp)
interfaces. When NETVIEW successfully queries the device, it defines a
range
of addresses to perform discovery. In our case, the address was 1.0.0.0
with
a mask of 255.255.255.0 (or similar, can't remember exactly). As a result,
many, many, many objects were added to the object database with a selection
name of "004325" or similar. I had to obtain an e-fix for this problem.
Basically netmon is creating "hints" for the objects he's going to discover
(but can't). When my object count got too high, OVw went nuts, smartsets
wouldn't keep current etc. Maybe this is your problem. I went back and
could
not find the PMR number but it might be 66843.

-----Original Message-----
From: Duble, Ethan [mailto:Ethan.Duble AT coopertools DOT com]
Sent: Monday, October 29, 2001 1:11 PM
To: 'IBM NetView Discussion'
Subject: [NV-L] ovwdb filling up with objects


Does anyone have a way to monitor what objects are getting put into ovwdb ?

for the longest time my object count sat around 1600 now its almost hit the
5000 mark, 500 objects over the weekend , 1000 over the last week,  3600
new
objects
we have discovery off , use a seedfile and nothing new is being added to
the
maps

due to the amount of customization we would like not to rebuild the
database
but i have convinced mgt that its gotta be done since this database is 2
years old covering all versions of netview from 5 + patch + ver 6 upgrade
and patches and aix upgrade from 4.32 to 4.3.3


currently we are running

aix 4.3.3 , neview 6.02

TIA

Ethan Duble
Coopertools











_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l