feibuergerenergie

Thx a lot for the quick reply and warning recomendation!

I reset the database with a backup. The very strange thing, then was:
In my (empty) “staging” phpMyAdmin account, I could upload the SQL dump without any issues. After having uploaded the – very same – dump into the (empty) productive account, rows with option_id = 0 in the _options table appeared. Guess what – now, the staging is the productive account.

Who knows. This thread’s issue is solved.

[Without having seen your screen shot before writing and doing this:]
Dunno where such a field may be hidden. I found the “A I” (auto increment) option and ticked it, however. And now it works perfectly.
Solved!
Thanks a lot anyways!!

• This reply was modified 2 months, 4 weeks ago by feibuergerenergie.

Thanks.
I get the result OK for all tables!
I analyze the tables, some get “table is already up to date”, and some OK (like the users table).

I tried optimize and repair, however. Both are not supported by (this) users table (and several others in the DB)!

• This reply was modified 2 months, 4 weeks ago by feibuergerenergie. Reason: typo

Thank you for the quick reply!
Well, I managed to delete the user with ID 0. That doesn’t help too much for the next intent, of course.
What exactly do you mean with “reparing”?
I roughly know how to survive in phpMyAdmin (and WebFTP and SQL language), basically, but what am I supposed to do …