This is probably caused by this PR, the result of a three day test session
pihole -g now uses a temporary database, to build the new gravity table. The content of the existing database is than copied over, the temporary database than becomes the live one.
I assume @DL6ER did NOT copy over all the tables, or the copy process has a bug.
I also wonder what happens if users are using the web interface, while pihole -g is running. should the database not be locked (+ warning) during pihole -g?