Background of the issue:
I was attempting to translate a job in the 'Translations' section of WPML, specifically a string Translation Job. The issue can be seen at hidden link.
Symptoms:
I encountered an error stating 'The translator could not be assigned to the job'. Additionally, there are database issues with error messages indicating that the index for tables 'QabwF_icl_translate' and 'QabwF_icl_string_translations' is corrupt, preventing database dumps.
Questions:
How can I resolve the issue of the translator not being assigned to the job?
What steps should I take to repair the corrupt index in the tables 'QabwF_icl_translate' and 'QabwF_icl_string_translations'?
Hi,
sorry, I haven't seen the private message before.
I have a backup from before I noticed any errors.
When I tried to restore only faulty tables, I found that the databse does not show an error anymore.
mysqlcheck wp_pbivh goes without errors.
Then I optimized table in phpmyadmin and db size shrunk from 60GB to 4.7 GB which is normal.
After this the backup went through as usual.
I did not restore backup now.
Shall I send you the backup file?
I can do automatic translations, but I cannot take string-translations. e.g. Job ID: 90790
"The translator could not be assigned to the job"
Is it still a DB issue?
Hi,
I just noticed, that all new jobs can be assigned to a translator.
So I cancelled all Jobs I had created on May 16th and will create new jobs. Then we will see if translations works fine.
I still don't know, what caused the issue and what really fixed it.
I am not sure what caused it, but there was an issue with your tables and SQL, not related to WPML. Since I could not access them even from SQL, it caused an error.
I would advise making a backup now when it works, and if it happens again checking with hosting, maybe they put some restrictions due to the size.
Hi Drazen,
thanks a lot.
We are taking backup every hour. So next time there is an issue, we will roll back immediately.
Thanks a lot again.
Kind regards
Johannes
