YES I HAVE!  BUT...

     no, there's no way to clean them up.  We have the same situation, and
     also ones that for some reason didn't get deleted but are now out of
     the Backtrack control file.  I have occasional ongoing discussions
     with Andy at ADSM support regarding this.  It is my belief that ADSM
     needs to implement a way for an admin to notoriously, explicitly,
     purposefully, delete an ADSM object.

     The best we could come up with was to change the filespace tag used by
     Backtrack, so that all new backups go under a different filespace
     name.  This required manual intervention whenever an old
     restore/archive needed to be recovered.  Then after some period of
     time.....clock still ticking....delete the old filespace.

     Hello, IBM?

     Al Barth,
     Sysadm
     Zurich Kemper Investments


______________________________ Reply Separator _________________________________
Subject: Cleanup ADSM file created from Datatools
Author:  Yar-Chung Wei <ywei AT LINDY.STANFORD DOT EDU> at ~Internet
Date:    6/26/97 11:23 AM


We are using Datatools SQL_Backtrack to backup our SYBASE and Oracle
databases and ADSM as our primary storage device.    Since we do drop some
databases or tablespaces occasionally, so we end up some orphanages ADSM
backup files which can not be deleted from ADSM GUI.  Datatools claimed that
there is no way they can delete these backup files in ADSM since database
names have already been removed from database system directory.  Has any
ADSM and Datatool's users there ever experenced the similar problems before
and who knows how to solve this issues, please let me know the solution.




Yar-Chung Wei
ITSS/OSS
Stanford University,