massive Zone Unavalable errors +more

[ChaosSlayer]

ok i did some mySQl manual reading - it seesm that problem is with the spawn2 table.

The table is InnoDB type - and from I understand this thing CANNOT BE just backed up, cuase the IDs of the primary key writen into file are not REAL IDs.
And if you EVER do any changes - like delete an entry and then back up the DB And if DB is later restored from backup - the whole thing (since it uses internal index table which is not shown to the user) and discover than enetry that supose to follow does nto exist - the whole thing crashes...

This mayby not very accurate (I am not mySQl expert), but i belive the problem is how to PROPERLY backup spawn2 table which was in any way altered so it will actualy WORK after restore..

Any mySQl experts can help with this????

[ChaosSlayer]

ok, this cost me a few grey hair (well few hair...), but with little mySQl expert help we solved this one....

PEOPLE!!! If you EVER delete or move ANY values in spawn2 tables using 1090 server build (INCLUDING using GeorgeS spawn editing tool) TURN OFF zone persistant state! Otherwise you will spend next 5 days drawing in error codes....

[Yeormom]

Thanks for sharing!

I spent longer than I should have looking for why the zone was trying to load a spawn with an id in the billions...