The element does not satisfy database criteria?

I am running Geographics 08.05.02.11 and work in a Tax Assessor's office where we link centroids of our parcel numbers to an oracle 9i db.  There are 2 Oracle Data Linkages created on each centroid when we link: 1) to a Feature table (Entity=2, MSLINK Key = 106) and 2) to a table in mscatalog called Parcel_Spatial (Entity=11, MSLINK is unique for each centroid).

Lately when I create a new centroid and try to link it to the db, the Oracle Data Linkages are not created for the centroids.  Using the Review Database Attributes of Element tool and clicking on the new centroid I receive the message "The element does not satisfy the database criteria".  Using the Element Information button, the Attributes tab shows a User Data Linkage but no Oracle Data Linkages.

A new database record is created in the Oracle Parcel_Spatial table, however.  I can query for max(mslink), then query the parcel_number for that max(mslink) and it is indeed my new centroid.  

Any help determining the problem establishing Oracle Data Linkages to my centroids would be appreciated.

Thanks.

Parents
  • Hello Cooper,

    Firstly, please do ensure that the GeoGraphics / MicroStation installation is supported together, and supported on the operating system in question.

    Secondly, can you elaborate on the process that you are using to create the feature definition (linkage), and the attribute linkage. While I would not expect a failure per se, if this is being done manually then one should be paying attention to the linkage mode utilized. The active linkage mode (new/duplicate/none) is exposed within the database settings dialog.

Reply
  • Hello Cooper,

    Firstly, please do ensure that the GeoGraphics / MicroStation installation is supported together, and supported on the operating system in question.

    Secondly, can you elaborate on the process that you are using to create the feature definition (linkage), and the attribute linkage. While I would not expect a failure per se, if this is being done manually then one should be paying attention to the linkage mode utilized. The active linkage mode (new/duplicate/none) is exposed within the database settings dialog.

Children
  • Hi Nelson,
    The Geographics/Microstation/OS combo has not changed and is the same as we've been using for the past decade so I think that should be fine.
    We have an mdl application that was created for us by a consultant many years ago that we use to link new centroids. There is a DB LINK button on this tool that is programmed to find objects on a certain level (level 61), and create new records in the parcel_spatial and feature tables in Oracle as well as establishing the attribute linkages on the centroid (the tool is hard coded for parcel_spatial table in mscatalog).
    This has worked fine for, like I say, a good decade. The only thing that has changed recently is we have bought some Bentley Map licenses within our county and some of those users sign onto our Oracle db through Bentley Map. I am not on Bentley Map yet, however; I am still using the same setup we have been using.
    Hope I'm making sense.Thanks.
  • Thank you Cooper.

    Alas, I can't comment on the custom tool itself, but you may be able to assess the behavior via:

    - running a MicroStation 'session debug' prior to engaging the tool/button:

    DMSG OPENMSGFILE c:\yourpath\yourfile.txt
    SESSION DEBUG ON
    (execute tool / perform steps to be debugged)
    SESSION DEBUG OFF
    DMSG CLOSEMSGFILE

    (the debug file will not be released, until the message file is closed)

    The session debug may reveal a database error code (ORA-....) or a/the failing SQL statement prior to a noted error.


    - running the commensurate GeoGraphics/MicroStation tools manually (e.g. attach feature, attach database linkage), in kind.

    Your mention of Bentley Map usage would only us to suspect some change to the database... so perhaps check to see if there have been any changes thus made to the tables/tablenames, or the related definitions within mscatalog (mscatalog.entitynum in particular).   

  • While not implied above, it is worth clarifying whether you are sharing the files in question between the GeoGraphics project and the Bentley Map schema(s).
    If it is so, know that this should not be done without specific planning. Bentley Map inherently deals with attribute / database linkages in a different manner than GeoGraphics/MicroStation.

  • I appreciate your replies, Nelson. I am currently working with the aforementioned consultant to see if we can resolve. Your thoughts have been most helpful. When we are able to resolve this issue I will update this thread. Thanks.