Hmm,
I had a similar thing recently, where I could not delete a systemobject
filespace because of problems with code release 4.2.4 handling a partial
object. However there were changes in the way partial objects are dealt
with in 5.1, and I now at 5.1.8 I have been able to successfully delete the
systemobject filespace.
Maybe this is what you are seeing.
Karel Bos
<[email protected]
om> To
Sent by: "ADSM: adsm-l AT vm.marist DOT edu
Dist Stor cc
Manager"
<[email protected] Subject
.edu> ANR9999D imexp.c(4574)
26/02/2004 14:44
Please respond to
"ADSM: Dist Stor
Manager"
<[email protected]
.edu>
Hi,
During expiration we get the following message:
ANR9999D
imexp.c(4574): ThreadId<71> Backup Entry for object 0.43293636 could not be
found in Expiration Processing.
Show object doesn't give anything back and delete object is failing also.
We
know what file space and node it is concerning. We tried to delete the file
space (systemobject) but that doesn't work either.
Anyone knows a good (clean and fast) way to get rid of this object (without
auditing the database)?
Regard,
Karel
**********************************************************************
The information in this E-Mail is confidential and may be legally
privileged. It may not represent the views of Scottish and Southern
Energy Group.
It is intended solely for the addressees. Access to this E-Mail by
anyone else is unauthorised. If you are not the intended recipient,
any disclosure, copying, distribution or any action taken or omitted
to be taken in reliance on it, is prohibited and may be unlawful.
Any unauthorised recipient should advise the sender immediately of
the error in transmission.
Scottish Hydro-Electric, Southern Electric, SWALEC and S+S
are trading names of the Scottish and Southern Energy Group.
**********************************************************************
|
