Transfer L2JOfficial to L2JServer
Posted: Tue Jan 19, 2010 5:55 pm
How I can transfer my sql ( chars, clans and etc. ) from l2jofficial to l2jserver?
L2J Server Discussion Board
https://www.l2jserver.com/forum/
Not at all... It's no true, at least if you do the update from version 1466 of l2jofficial. For one hand, the automatic processor has too many errors. For the other hand, a manual processor is so hard and so difficult that everybody can say that it is impossible to migrate from l2jofficial to l2jserver without problems.janiii wrote:You can use the same db just be sure to run database upgrade and automagic update. And make a backup of whole db before!
Code: Select all
ERROR 1091 (42000) at line 1: Can't DROP 'acc'; check that column/key existsERROR 1060 (42S21) at line 1: Duplicate column name 'change_weaponId'ERROR 1054 (42S22) at line 1: Unknown column 'access_level' in 'accounts'ERROR 1060 (42S21) at line 1: Duplicate column name 'transform_id'ERROR 1054 (42S22) at line 1: Unknown column 'obj_Id' in 'characters'ERROR 1091 (42000) at line 1: Can't DROP 'price_sell'; check that column/key existsERROR 1091 (42000) at line 1: Can't DROP 'siegeDayOfWeek'; check that column/key existsERROR 1091 (42000) at line 1: Can't DROP 'item_skill_id'; check that column/key existsERROR 1060 (42S21) at line 1: Duplicate column name 'leader_id'ERROR 1054 (42S22) at line 1: Unknown column 'obj_Id' in 'characters'ERROR 1054 (42S22) at line 1: Unknown column 'access_level' in 'access_levels'ERROR 1054 (42S22) at line 1: Unknown column 'skill_id' in 'custom_armorsets'ERROR 1054 (42S22) at line 1: Unknown column 'skill_id' in 'custom_armorsets'ERROR 1060 (42S21) at line 1: Duplicate column name 'drop_herbs'ERROR 1060 (42S21) at line 1: Duplicate column name 'systime'ERROR 1091 (42000) at line 1: Can't DROP 'siegeDayOfWeek'; check that column/key existsERROR 1146 (42S02) at line 1: Table 'l2ethernal.augmentations' doesn't existERROR 1054 (42S22) at line 1: Unknown column 'in_jail' in 'characters'ERROR 1060 (42S21) at line 1: Duplicate column name 'fortType'ERROR 1091 (42000) at line 1: Can't DROP 'char_name'; check that column/key existsERROR 1091 (42000) at line 1: Can't DROP 'karma'; check that column/key existsERROR 1060 (42S21) at line 1: Duplicate column name 'fame'ERROR 1091 (42000) at line 1: Can't DROP 'oldname'; check that column/key existsERROR 1060 (42S21) at line 1: Duplicate column name 'time'ERROR 1091 (42000) at line 1: Can't DROP 'time_left'; check that column/key existsERROR 1060 (42S21) at line 1: Duplicate column name 'blood'ERROR 1060 (42S21) at line 1: Duplicate column name 'bookmarkslot'ERROR 1060 (42S21) at line 1: Duplicate column name 'classIndex'ERROR 1060 (42S21) at line 14: Duplicate column name 'mw_legs'ERROR 1091 (42000) at line 1: Can't DROP 'html'; check that column/key existsERROR 1060 (42S21) at line 1: Duplicate column name 'enchant4_skill'ERROR 1091 (42000) at line 1: Can't DROP 'skill_name'; check that column/key existsERROR 1060 (42S21) at line 1: Duplicate column name 'vitality_points'ERROR 1091 (42000) at line 1: Can't DROP 'skill_id'; check that column/key existsERROR 1060 (42S21) at line 1: Duplicate column name 'depositable'ERROR 1060 (42S21) at line 1: Duplicate column name 'showNpcCrest'ERROR 1060 (42S21) at line 1: Duplicate column name 'createTime'ERROR 1060 (42S21) at line 1: Duplicate column name 'title_color'ERROR 1091 (42000) at line 1: Can't DROP 'friend_name'; check that column/key existsERROR 1060 (42S21) at line 1: Duplicate column name 'relation'ERROR 1060 (42S21) at line 1: Duplicate column name 'additionalname'
May be, but in my case, this is going to make check me each and every of the tables. I do not rely that in a future, the server will crush... I supose that as my situation, may be many people. And I'm sure that with a note, or an officieal explanation, that those types of mistake are "correct"._DS_ wrote:Those "errors" are normal parts of update process because tables already converted and contain/removed those fields.
(You write too fast..._DS_ wrote:if database have still wrong structure