LIBRARY MANAGEMENT

[nibola]

Good morning,

I have a problem with the management of some of some assemblies. Something happened and, in some parts and sub-assemblies, in the "related items" list appears a relation calles "has moved to". This relation doesn't allow me to do a check out of the part or assembly, I cannot update it and I cannot download any bigger assembly that contains this subassembly or part. I have tryed to do a new version and then "update in library" but doesn't work, a message appears saying "The item can not be approved, you must first assign a value to all required atributes (i.e. part number)
I-deas 11NX Series m4.

Any suggestion, advice please?

Thank you and best regards

 

[WH74]

it's been ages, but GTAC can fix this.

it's either a move was not completed because something crashed when checking in or out. I library check with dmadmin tool can help you find and fix this. Don't hold me to this but i think deleting the chk out and library clean is what fixes this.

Or

I-deas create a temporary file for every library action and it's supposed to overwrite the files once is cycles though all the possibilities. but sometime it uses all the possible names (I think there are 10000 possiblities, project or library name with a 4 digit appended to it.) These files can be deleted and all is well. This is something that you will have to do every once in a while.

 

[nibola]

Good afternoon

Thank you for your answer.
Still not able to solve the problem. You are right, the problem occured when the system chrashed in a check in or check out, or when moving some items from one project to another one.
We have been cleaning, checking and running the diag tool with the dmadmin, but problem is still there. And also the problematic parts are not in check in or check out. Even we have tried to reconnect the files with new parts.
These files that you talk about (temporary files for every library action), where are they placed?
New ideas will be welcomed.
Thank you anyway.
Best regards

 

[WH74]

Ok, it sounds like it is not the second issue. I have not been using i-deas for some time so i don't recall what exactly you need to look for.

If i recall i think the message window or the dmadmin tool will tell u what files it is having issues with.

I think you have to delete the file on the OS level and then run the dmadmin tool to clean, check and fix the tdm.

You should be able to do a search for files that have a lock or say they are in a move state. I am not sure here, going on memory. I am thinking that you may see the same file in two locations in the tdm and they both have locks on them. it should be in the move from library and the target library. I don't know if they point to the same file on the OS or not. I think one of them gets deleted, and a clean of the tdm fixes it. I am not sure how this will relate to a model file. I think you can delete the model files.