As far as I know, there is not a real tool for doing this; generally I find the
need to do this early in
the impementation and I am still willing to flush the database and rediscover.
However, after doing
the big cut/paste, I would suggest this: Use the Locate function to find all
the now-unwanted nodes, or
chunks of them; (probably selected by Attribute); Use
View...Highlights...Select Highlights; now they
are selected. (check the Locate...Selected Objects List as a sanity check);
then Edit.. Delete... From
All Submaps.
If you have multiple maps, you might check the trapd.log for a list of nodes
that were deleted as a
result of this activity, and make a script to run ovotopofix -r <selectionname>
against them. Then
open the other maps and let the deleted objects synchronize out.
Generally I plan on doing a number of flushes as I refine the seedfile and
don't invest too much time
on cutting and pasting until I'm pretty sure of the seedfile, so I don't have
to go through the manual
cleanout.
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
(248) 552-4968 Voicemail, Fax, Pager
---------------------- Forwarded by Leslie Clark/Southfield/IBM on 11-01-98
08:41 PM ---------------------------
NV-L@UCSBVM.UCSB.EDU on 10-31-98 06:25:25 AM
Please respond to simon@nettrack.com.au
To: NV-L@UCSBVM.UCSB.EDU
cc:
Subject: Cleaning up after seed file revisions
Hi,
I am interested in the issue of how you might clean nodes out
that are already discovered using your previous seed file, when
you have just added in significant changes to said seed file and
activated them. It seems that the seed file will not automatically
remove the nodes which are now excluded from discovery. I
am OK with the manual procedure of deleting nodes from all of the
maps for one or two nodes but I am hoping there is some
standardised procedure or facility to help me trim the databases
quickly following more sweeping changes.
Thanks very much,
Simon Long
Nettrack Technical Solutions Pty Ltd
|