Hello Community,
I'm wondering about what's happening sometimes in our LIVE Workspace.
We've got plenty version enabled tables, each with one primary key column (Prior to versioning) named MSLINK.
After versioning the primary key is a combination if the origin PK and the VERSION attribute.
When I look into the tables ALL_CONSTRAINTS and ALL_CONS_COLUMNS I see these two attributes as primary key, but they are disabled,
when I look into ALL_WM_CONSTRAINTS the primary key is flagged as enabled.
My problem is that recently I found some duplicate datasets with all attributes the same, MSLINK and VERSION included.
These attributes are in our LIVE Workspace and they even have the same NEXTVER value (-1).
Is the Primary key still activated, is that made by design or am I doing something wrong when versioning our tables?
The Database I'm talking about is on the latest 11g version.
Thank you in advance,
Maik