Transfer L2JOfficial to L2JServer

[L2Noob]

How I can transfer my sql ( chars, clans and etc. ) from l2jofficial to l2jserver?

[janiii]

You can use the same db just be sure to run database upgrade and automagic update. And make a backup of whole db before!

[ThyraRexx]

You can use the same db just be sure to run database upgrade and automagic update. And make a backup of whole db before!

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.
The solution may be to check table for table, and do the changes by hand. Of course, with the "bad taste" that the old staff of l2jofficial has abandonated their all followers without a metodology to migrate our servers to l2jserver...

[Gnacik]

when we `drop` l2jofficial project and some1 use latest stable enough was run update database with automagic process. don't blame us for your delay. we are working hard here right now and with every revision is harder to change from l2joff to l2js.

[ThyraRexx]

Sorry but i don't try to blame nobody. I only have said something that you can verify with a little effort. I try to consult the magnific forum, to find a note that I posted in it. But, I can't neither login me in the forum, nor recovering my password (it may be lost, but i don't believe it...).
I know the big effort that the l2jofficial's staff has done. I have no words to explain my gratitude. I will be always grateful by your effort used in the server, but the migration to l2jserver is not not clear at all.

For example, the log doing that you have just said, from version 1466 of l2jofficial to version 6984 (???) of l2jserver:

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' 

(However, the server start, but I supose that it`s easy to think about the insecurity that so many mistakes, in order to open an Epilogue Server...)

Thank you for your effort but in this case, I believe that you could have made it better.

P.D. Sorry for my english. You know that it isn't my native language...

[_DS_]

Those "errors" are normal parts of update process because tables already converted and contain/removed those fields.

[Gnacik]

as _DS_ say. its normal. automagic proces run all updates. and cannot drop something if its dropped already. or cannot add column if that column already exists. if you make update with automagic proces just run server and look into logs. if database have still wrong structure probably you can find some error in logs. if not all will be working corectly.

[ThyraRexx]

Those "errors" are normal parts of update process because tables already converted and contain/removed those fields.

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".

Thanks a lot.

if database have still wrong structure

(You write too fast... )That's the problem. I haven't got the security that my bd is correct...
And I execute by hand the updates since my server database. And I get similar mistakes: colums that already exists, duplicate columns and so on... (Many nerves in the process... )

[jurchiks]

lol, all "can't drop", "unknown" and "duplicate" errors are normal and are not REAL errors, more like warnings
don't bother checking each of them, there's nothing wrong
it's easier doing the update and then testing in private if all stuff has remained, if you really are that paranoid

[djbenny]

converted manny times form 1507 l2joff "Final" to latest l2j "GE".
without a single problem/error.

[ThyraRexx]

OK, i believe that i just find a solution. I has tested the migrated datapack with those warnings/errors, and I don´t find any several errors. Only just a few of ones, but easy to correct. But to be sure, i probe the next. I open two servers: one the migrated bd, other a new bd. I probe to pass a character from one to other with the gm's pannel, and I tested that all is correct . Any warnings in the log, but all skills, items, quest... everything is correct!!! (Only for one player, but I suppose that they all will be equal.)
In a server with few players, it is easy. In a big server, may be more work... but this may be a solution for a paranoid person with the safety, as me...