Thanks for the info.

We are currently in the process of going to TDP for MS SQL Server 5.1*.
Your theory about the Dbname case sounds logical.

Yi

>>> hoobler AT US.IBM DOT COM 04/16/03 12:11PM >>>
Yi,

Data Protection for SQL version 1.1
went out of service over a year ago (1/30/2002).
I would advise that you look into the
latest versions.

As for the problem below, it looks like there were
some database backups that have characters in the
database name that aren't being recognized,
or the case of the database is lower and
the backup was upper case... or something
strange about the database name itself
(unsupported characters, international characters, etc.)

The side effect is that you won't be able
to expire those backups and they will remain.

You can try calling support, but I am not
sure how far you will get since this has been
out of service for so long.

Thanks,

Del

----------------------------------------------------

Del Hoobler
IBM Corporation
hoobler AT us.ibm DOT com

- Remember that the best job security is
doing a job well and doing it cheerfully.

=====================================================
I am receiving following error messages in sqlauto.log.
04/16/2003 03:42:38,ANS1088E (RC124)  File space '' does not exist
04/16/2003 03:42:38,Database : error, Object Name : 03062003025327.db,
status : ACO3019E -- An error was encountered.
04/16/2003 03:42:38,ANS1088E (RC124)  File space '' does not exist
04/16/2003 03:42:38,Results: 70 backup object(s) of 2334 examined were
deleted.
04/16/2003 03:42:38,ANS1088E (RC124)  File space '' does not exist

Our retention date is 32, and we are prunning the backup files related to
the particular database, except for the one above.
What can we do to clear up the error message?