database problems could not be repaired

Have you ran the WooCommerce database update that was in an alert after upgrading to WooCommerce 2.6?

And if so, what do you see in the db-update logs at WooCommerce > System Status > Logs?

i think so but i do not remember it .

this is in the : wc_db_updates-210a2ee42a94f5cc219747fd63dd59ab.log (4 luglio 2016 9:38)

07-04-2016 @ 11:38:29 – Queuing 2.6.0 – wc_update_260_options
07-04-2016 @ 11:38:30 – Queuing 2.6.0 – wc_update_260_termmeta
07-04-2016 @ 11:38:30 – Queuing 2.6.0 – wc_update_260_zones
07-04-2016 @ 11:38:30 – Queuing 2.6.0 – wc_update_260_zone_methods
07-04-2016 @ 11:38:30 – Queuing 2.6.0 – wc_update_260_refunds
07-04-2016 @ 11:38:30 – Queuing 2.6.0 – wc_update_260_db_version
07-04-2016 @ 11:38:31 – Running wc_update_260_options callback
07-04-2016 @ 11:38:31 – Finished wc_update_260_options callback
07-04-2016 @ 11:38:31 – Unable to dispatch WooCommerce updater: Operation timed out after 1000 milliseconds with 0 bytes received
07-04-2016 @ 11:38:32 – Running wc_update_260_termmeta callback
07-04-2016 @ 11:38:32 – Finished wc_update_260_termmeta callback
07-04-2016 @ 11:38:32 – Running wc_update_260_zones callback
07-04-2016 @ 11:38:32 – Finished wc_update_260_zones callback
07-04-2016 @ 11:38:32 – Running wc_update_260_zone_methods callback
07-04-2016 @ 11:38:33 – Finished wc_update_260_zone_methods callback
07-04-2016 @ 11:38:35 – Running wc_update_260_refunds callback
07-04-2016 @ 11:38:35 – Finished wc_update_260_refunds callback
07-04-2016 @ 11:38:35 – Running wc_update_260_db_version callback
07-04-2016 @ 11:38:35 – Finished wc_update_260_db_version callback
07-04-2016 @ 11:38:35 – Data update complete

Try deactivating WooCommerce and activating it again to see if that resolves the issue with the table.

done .
but still the same problem .

Oh, mis-diagnosed this at the beginning – sorry. The woocommerce_termmeta table should no longer exist. Another extension must still be trying to use it and needs to be updated.

Try temporarily disabling all plugins except for WooCommerce. If that resolves the issue, then slowly re-enable plugins until you find the one that’s causing this error.