nv-l

Re: AW: CLI for node deletion

1999-10-07 07:38:30
Subject: Re: AW: CLI for node deletion
From: MICHAEL_IMHOFF AT HP-DENMARK-OM1.OM.HP DOT COM
To: nv-l AT lists.tivoli DOT com
Date: Thu, 7 Oct 1999 13:38:30 +0200
     Note that objects are first deleted from the object database when all  
     references from the topology database and all map databases are gone.
      
     - Michael.


______________________________ Reply Separator _________________________________
Subject: AW: CLI for node deletion
Author:  Non-HP-Stefan.Beck (Stefan.Beck AT HVBINFO DOT COM) at 
HP-Belgium,mimegw3
Date:    07-10-99 13:09


I think you're right, but since NetView consists of more than one database,
this is not the whole truth:

ovtopofix -r seems to delete an object from the topology-database
ovwdbdmap -d seems to delete an object from the object-database


WARNING: You should know what you are doing, when you're going to use these
commands.  
Especially you should be very familiiar with internals of the Netview
Databases
( it's obvious why they're not dokumented).
In most cases you'll leave the databases in an inconsistent state (these
commands  
a.f.a.i.k. don't care about child or parent object relationships in the
databases)
REMEMBER: You'll get no support from Tivoli, when issueing these commands.

regards
Stefan

> -----Ursprüngliche Nachricht-----
> Von:  Jane Curry [SMTP:jane.curry AT SKILLS-1ST.CO DOT UK]
> Gesendet am:  Donnerstag, 7. Oktober 1999 13:17
> An:   NV-L AT UCSBVM.UCSB DOT EDU
> Betreff:      CLI for node deletion
>  
> Does anyone have a way to delete a node entirely from NetView, using the
> command line interface??  ovtopofix -r seems to have the desired effect,
> followed by an ovtopofix -a but I know the -r flag is distinctly
> unsupported.
>  
> Any comments appreciated,
> Jane
> --
> Tivoli Certified Enterprise Consultant
> Skills 1st Limited, 2 Cedar Chase, Taplow, Bucks, SL6 0EU, UK
> Tel: +44 (0)1628 782565
> Copyright (c) 1999 Jane Curry <jane.curry AT skills-1st.co DOT uk>.  All 
> rights
> reserved.


<Prev in Thread] Current Thread [Next in Thread>