How to resolve '*** DATABASE ERROR: Column not found' in Model Manager

Forum|Forum|9 years ago
April 18, 2017
14 replies
6166 views

Dear users,

we use Direct Modeling 19M060 with Model Manager. I have a construction which contains parts that were downloaded from a supplier (Festo in this case). The parts seem to have some kind of link to a part library. Because they give the following error:

I have pasted the details in the attachment of this message. Key of it are the following lines I think.

class com.osm.exception.WMKernelException: 91002211: *** DATABASE ERROR: Column not found

Thread = RefreshController - doing refresh ID= 33

SQL [SELECT INFOS FROM LIBRARY_3D WHERE LIBRARY_3D.MODEL_ID_NAME IN ('PSOL_651849_MS_LR_20','PSOL_376409_MS6_MV__2_','PSOL_527682_MS6_EE_1_2_10V24_S1D','PSOL_175250_PEV_1_4_B_OD','PSOL_6844_U_1_2_B','PSOL_KOND_MS6_1_3','PSOL_532195_MS6_WP__w_','PSOL_527676_MS6_FRM_1_2_Y1P1','PSOL_526490_MS6_LFR_1_2_D7_ERV_AS1D','PSOL_374264_MS6','PSOL_534153_ESK_1_4_1_2')]

Does anyone have a clue how to solve this?

Thanks,

BS

1_error-details-txt.zip

General

Best answer by MaxR.Kublin

Check if the table LIBRARY_3D has the attribute (=column) MODEL_ID_NAME

(I guess it does NOT)

M

MaxR.Kublin

Answer

13-Aquamarine

Check if the table LIBRARY_3D has the attribute (=column) MODEL_ID_NAME

(I guess it does NOT)

B

bschoondermark

Author

1-Visitor

I sort of knew this already, but I never thought of just adding the column in the sql table.

It's a workaround that works nonetheless!

Thanks,

BS

M

MaxR.Kublin

13-Aquamarine

Well, I did not want to propose that you just add the column to the table in the database.

If Model Manager tries to access the MODEL_ID_NAME column, this indicates that the column MODEL_ID_NAME is registered in the XML-File of Model Manager.

There are two "real" solutions:

1) Add the MODEL_ID_NAME column through the Model Manager Admin U/I (or through the legacy Workmanager U/I)

2) Modify the XML File to *not* use the MODEL_ID_NAME (use NAME instead).

By just adding the MODEL_ID_NAME column to the LIBRARY_3D table you have created an inconsistency with the contents of table WM_ATTRIB_COL

(which contains description of all tables/columns of a Model Manager Schema).

Be prepared for other surprises with Library Parts.

T

ThomasKirkman

16-Pearl

We use this lisp program when we load parts created by a .lsp file. This keeps the parts from being made into library parts. The alternative is to load the goody "sl_remove_sl". This will add a command to the toolbox that will strip the library status of the imported part.

Regards

Tom

1_lisppart-lsp.zip