JamesThorpe Posted March 12, 2014 Report Share Posted March 12, 2014 I keep a copy of our repository on my laptop, and occasionally synchronise it with our main server. This morning I got an error during synchronisation due to the database file size limit being reached - I hadn't realised I'd left it on the built in SQL CE. I've migrated it to SQL, and gone to re-run the synchronise to pull the branches in (there were no pushes) and all has now worked, apart from one branch which is throwing the following error: Violation of PRIMARY KEY constraint 'PK_object'. Cannot insert duplicate key in object 'dbo.object'. The duplicate key value is (495292). Any ideas on what may have caused this and, more importantly, how to solve it so I can proceed? Thanks, James. Link to comment Share on other sites More sharing options...
cidico Posted March 12, 2014 Report Share Posted March 12, 2014 Hi James, Do you have In your laptop any changes that are not in the main server? If not, just remove the repository, create a new one and then sync again. There are a some different ways of "getting the changes back". The first one is going back to SQL CE backend and then fast export and fast-import the SQL CE repository into a new backend repository. Here is a link on how to work with fast-export / fast-import: https://www.plasticscm.com/infocenter/technical-articles/kb-fast-import-fast-export.aspx Hope it helps Link to comment Share on other sites More sharing options...
JamesThorpe Posted March 12, 2014 Author Report Share Posted March 12, 2014 No, there's nothing currently on my laptop that would stop me from starting again - would just like to know what might have happened really so it doesn't happen again at a more critical time! I'm not sure I could go back to a sql ce backend again - 160 other branches pulled successfully, so the db files are almost certainly too big to go back again now. Link to comment Share on other sites More sharing options...
cidico Posted March 12, 2014 Report Share Posted March 12, 2014 There are a few methods available to get data back. You can always go back. In the administration tool, you can pick the SQL Server CE again and this will work just fine. Plastic does not lose any files and the SQL CE database files are still in the server folder. Link to comment Share on other sites More sharing options...
JamesThorpe Posted March 12, 2014 Author Report Share Posted March 12, 2014 The reason I had to go to the SQL backend was because the CE database files had hit the 4gb file limit - once transferred to SQL, I pulled some branches in - so are probably too big to go back to SQL CE again now. As you say - starting again is probably the easier solution! Link to comment Share on other sites More sharing options...
manu Posted March 17, 2014 Report Share Posted March 17, 2014 Which Plastic SCM version are you using? we recently fixed and issue pretty similar than the one you are facing so please upgrade to the latest public release and try again before starting from scratch. Link to comment Share on other sites More sharing options...
JamesThorpe Posted March 28, 2014 Author Report Share Posted March 28, 2014 Hi Manu, Thanks for the reply. We're on 5.0.44.528. I started a new repo and tried replicating again, but I'm now hitting the same issue on a different branch. Also my colleague who also synchronises locally has just hit the same problem today. Was it fixed in a more recent version than this? Will gladly update and give it a go. Cheers, James. Link to comment Share on other sites More sharing options...
JamesThorpe Posted March 28, 2014 Author Report Share Posted March 28, 2014 Just upgraded and resynced - all fine this time, thanks Manu Link to comment Share on other sites More sharing options...
manu Posted April 1, 2014 Report Share Posted April 1, 2014 Greeeeeeat!!! Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.