unable to rem node: Inv. references still exist

ap0010

ADSM.ORG Member
Joined
Jun 27, 2007
Messages
6
Reaction score
0
Points
0
Location
Berlin, Germany
Website
www.fhi-berlin.mpg.de
Hello,
after deleting all files by del filesp Type=any, and Type=spacemanaged, when I remove the node,
I get the message: ANR2152E Inventory references still exist ...

What inventory references other than files could still exist?
Any idea how I can remove the node?

Thank you for any hints:p
 
Hello,

when you use the command q filspace "nodename", do you see any filespace for the client ???
 
thought that all files are gone (by the del filesp command),
but there is one filesp left:
SystemObjec1 WinNT Unicode Capacity and Util =0
 
Last edited:
OK,

you must del the named filespace. the command is del filespace nodename filespacename.

god luck ....
 
Referenced to expiring objects:

As you can see from the following actlog,
nothing is deleted, because the process refers
to itself: "referenced in Expiring Objects".

Anybody some idea except calling support?


06/27/07 15:56:37 ANR2017I Administrator PREUSSER issued command: QUERY
ACTLOG begint=-0:06 (SESSION: 8412)
06/27/07 15:57:52 ANR2017I Administrator PREUSSER issued command: DELETE
FILESPACE LUCKY-OLD.RZ-BERLIN.MPG.de 13 namet=fsid
(SESSION: 8412)
06/27/07 15:57:57 ANR2017I Administrator PREUSSER issued command: DELETE
FILESPACE LUCKY-OLD.RZ-BERLIN.MPG.de 13 namet=fsid
(SESSION: 8412)
06/27/07 15:57:57 ANR0984I Process 146 for DELETE FILESPACE started in the
BACKGROUND at 15:57:57. (SESSION: 8412, PROCESS: 146)
06/27/07 15:57:57 ANR0800I DELETE FILESPACE SYSTEM OBJEC1 (fsId=13) for node
LUCKY-OLD.RZ-BERLIN.MPG.DE started as process 146.
(SESSION: 8412, PROCESS: 146)
06/27/07 15:57:57 ANR0802I DELETE FILESPACE SYSTEM OBJEC1 (fsId=13)
(backup/archive data) for node LUCKY-OLD.RZ-BERLIN.MPG.DE
started. (SESSION: 8412, PROCESS: 146)
06/27/07 15:57:57 ANR9999D imfsdel.c(2832): ThreadId<46> nodeId=2, fsId=13
not deleted: referenced in Expiring.Objects (SESSION:
8412, PROCESS: 146)
06/27/07 15:57:57 ANR9999D ThreadId<46> issued message 9999 from: <-
0x00000001015F4724 outDiagf <- 0x0000000100A3B6EC
DeleteFileSpace <- 0x0000000100A32470 imFSDeletionThread
<- 0x000000010008A0CC StartThread <- 0xFFFFFFFF7EB181A8
*UNKNOWN* (SESSION: 8412, PROCESS: 146)
06/27/07 15:57:57 ANR0806I DELETE FILESPACE SYSTEM OBJEC1 (fsId=13) complete
for node LUCKY-OLD.RZ-BERLIN.MPG.DE: 0 objects deleted.
(SESSION: 8412, PROCESS: 146)
06/27/07 15:57:57 ANR0985I Process 146 for DELETE FILESPACE running in the
BACKGROUND completed with completion state FAILURE at
15:57:57. (SESSION: 8412, PROCESS: 146)
 
I think that the system objects in expiring mode. have you run an expiration on your system ???
 
Expire inventory runs regularly, every week once, but not at this moment.
Last time it ended in error: ANR9999D Bitfile id ... not found.
How can I get rid of these data base entries? May be that is related to our problem.
 
Could try running expiration and then try the del filespace again once that's finished.

But I suspect you really have DB corruption there, especially given the bitfile error. Probably time to call IBM support and do some audit db's.

Also, why does your system object come up as "SYSTEM OBJEC1" ie a 1 instead of a T in OBJECT? It looks like this filespace was previously imported from an export and tsm renamed it due to there already being a system object.
 
Back
Top