Duplicate OIDs within the same Database

[muren400]

Hi,

not sure if this is actually a bug or not, but I read somewhere in the wiki, that oids should be unique within a database. Nonetheless I stumbled upon two different IfcProject entries that share the same oid. Is this a very unusual glitch that one should be concerned about or can there be duplicate oids for different revisions?

Thanks,
Andreas

PS.: this happened in 1.5.182

[hlg]

Depends on how the two IfcProject entities are "different". If you create revisions by using the low level interface, then yes - you will have one stable oid for an entity throughout different revisions (see Database versioning). In that case, the two IfcProject entities wouldn't actually be "different". Otherwise I think it is rather unexpected.

[muren400]

It's two different IFC Files checked in into two different subprojects.

[muren400]

There were two rollbacks during the checkin of the first model. The Server was restarted twice before the checkin of the second model.

[zaqifathis]

I attempted to reproduce the issue using BIMserver 1.5.185 but was unable to replicate the same results. I am not sure if that happened because of the error you have during the first checkin.

[hlg]

This will be difficult to reproduce. @muren400, do you still have access to that data and logs? Which serializer did you checkin with (streaming?) and which database exceptions caused the rollbacks? If StreamingCheckinDatabaseAction.rollback was triggered, there should be something in the logs as well. From my understanding, duplicate OIDs for different entities in one database could indeed have unpredictable consequences down the line and is not something that is handled gracefully.

[muren400]

We are using the streaming deserializer. Unfortunately we do not have those logs anymore.
I'm also not aware of this happening again since then.