OLE DB duplicate key value error

[Guillaume]

Hi,

We've got a project on SQL Server + Version control. Users have a shared access running Checkouts/checkins on controlled packages.

They've experienced the following OLE DB error message : cannot insert duplicate key row in object dbo.t_operation with unique index UX_operation_ea_guid. the duplicate value is...

As it currently stands, all the class operations have been lost in the project, despite the fact that these operations exist in the controlled XML file.

Is this issue related with a DB config issue (e.g. in the SQL scripts to generate the tables), a use of the version control (some users run a Get Latest), or else?
Would it be recommended and safe to run a Project DB Integrity Check?

Thanks

[Geert Bellekens]

Guillaume,

What happened?
Probably the best thing to do right now is to restore an SQL Server backup and then rollback all check-ins done after the date of the backup.

Someone must have done something weird to have triggered this.
First check if the operation with the given guid is not duplicated across the xmi files.
I can imagine that a combination of moving operations + check-out/undo checkout etc... might get you into trouble

If you don't want to go for the backup option you might also be able to restore the model by importing the previous versions of your xmi files into the model.

Geert

[qwerty]

I've seen that in the past but too long ago. Try Tools/Data Management/..Integrity...

q.

[Guillaume]

thanks for both your inputs - I don't have access to this project at the moment so I'm going to suggest running a DB first and keep the previous ones, before attempting the Integrity Check first.

I also need to gather more info

cheers

[qwerty]

The integrity is at no risk, though the dialog suggests it would. You should run it regularly anyway on a - say - weekly basis.

q.