The metCharacterNames table is used to store a mapping of ID's to names (characters, corporations, alliances, etc). That table is created when needed in the main database. Unfortunately, upgrading the database for a new release will lose all of the data in the metCharacterNames table.
The table was put in the main database rather than the individual character databases so that any duplicate values would not need to be downloaded for each character.
Possible solutions are:
1) Move the table to the character database.
2) Create a new database at the top level of the Vitality directory.
3) Dump all data from the table before upgrading the database and restore it afterward.
The metCharacterNames table is used to store a mapping of ID's to names (characters, corporations, alliances, etc). That table is created when needed in the main database. Unfortunately, upgrading the database for a new release will lose all of the data in the metCharacterNames table.
The table was put in the main database rather than the individual character databases so that any duplicate values would not need to be downloaded for each character.
Possible solutions are: 1) Move the table to the character database. 2) Create a new database at the top level of the Vitality directory. 3) Dump all data from the table before upgrading the database and restore it afterward.