The translation memory data file engine returned an error: constraint failed UNIQUE constraint failed: fuzzy_data.translation_memoryJd, fuzzy_data.translation_unit_id

Hello!
When I try to re-index a TM or export it to tmx I got this error.

Trados Studio error message stating 'The translation memory data file engine returned an error: UNIQUE constraint failed: fuzzy_data.translation_memory_id, fuzzy_data.translation_unit_id'.



Generated Image Alt-Text
[edited by: Trados AI at 2:20 PM (GMT 0) on 5 Mar 2024]
emoji
Parents
  • Hello,

    I understand you're encountering an error when trying to re-index a translation memory (TM) or convert it to TMX. This error is related to a unique constraint failure in the fuzzy_data table of your TM database.

    Here's a step-by-step guide to help you resolve this issue:

    Step 1: Make a backup of your TM. This is a crucial step to prevent any data loss.

    Step 2: Try to repair the TM. You can do this within Trados Studio by going to the Translation Memories view, right-clicking on the problematic TM, and selecting 'Repair'.

    Step 3: If the repair doesn't work, you might need to create a new TM and import the TMX of the old one into it. To do this, first, export the problematic TM to a TMX file. Then, create a new TM and import the TMX file into it.

    Step 4: If you're still encountering issues, you might need to use the "Prepare without Project TM" batch task sequence or any other that does not create a Project TM, as suggested in the context provided.

    Please note that our development team is aware of such issues and is working on a fix.

    I hope this helps! If you have any other questions or need further assistance, feel free to ask.

    Best regards,

    RWS Community AI

    emoji
  •  

    A little bit of hallucination from the TradosAI tool, but it's on the right lines.  There is no repair option for TMs built into Trados Studio.  But you can do this using this app:

    https://appstore.rws.com/Plugin/41

    Try that and see if it helps.  There is no guarantee with TMs but looking at your error it does appear as though your TM may be corrupted.

    Please note that our development team is aware of such issues and is working on a fix.

    Also hallucination.  There is nothing the developer team can do to ensure your T doesn't get corrupted.  There are too many external influences that cause this over which we have no control... such as sharing a TM with others via a shared drive?  That's probably the most common reason for corrupt TMs, but it can also happen if you have your TM on a cloud drive such as OneDrive; depending on your settings the TM can become unavailable to Studio and the writing of new TUs to the TM whilst it's synching and updating in the cloud can also corrupt a TM.

    Paul Filkin | RWS Group

    ________________________
    Design your own training!

    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

    emoji
  • Hello Paul

    Problem is already solved. I downloaded the SDLTM repair application from the Store.

    emoji
Reply Children