I am still having problems expiring my old Sybase database
backups. The initial problem was that the control files on
the client were missing the "generations" parameter (this
parameter indicates how many versions to keep, and gets SQL
backtrack to tell ADSM when it no longer needs a previous
backup).

No problem, I add it to the control file and create a new
management class specifically for the database. This management
class keeps extra versions and only versions for 0 days.

When the expiry runs, I get messages saying that management
class ABC no longer exists in domain NEWDOM. My predecessor
had created a domain in which the data was kept for 60 days.
In December I created a new domain with a new management class
to keep data for 7 days. In the new domain I have different
names for the management classes. So, ADSM reports the default
management class attributes will be used for expiring the data.
The default management class is different from the database
management class and is intended for the OS.

I decide I do not want to wait a whole week before seeing if
my new changes to the control files work and create a new
management class called ABC as well. This mc keeps all versions
for 0 days, ie deletes immediately. I do this so that ADSM
does not use the default management class.

The results so far have been nothing. I do not seem to be
deleting any of the old backups! Do the old backup versions
keep their old management class attributes and do I have
to wait 60 days for the first data to expire??

If anyone can give me some insight on how to get rid of those
old backups I would greatly appreciate it. The old backups are
taking up far too much valuable tape space.

Naomi van Roosmalen
NBTel