Problems after updating SQL

[neiv2]

After updating my server code per Trevius' instructions here (and after having neglected the updates for quite a while) I am receiving a "that zone is unavailable" message when I attempt to enter the world from the character select screen.

Updating the SQL did not go off without a hitch, unfortunately. I first updated only the sql statements that were included in the change log, but not the svn sql references. So I went back through the change log and redid all sql statement and svn sql. I received many error massages ("table does not exist"; "duplicate entries", etc.) through that process; and in at least one case the file referenced in the change log (viz., 229_spells_table.sql) did not exist--so I used 230_spells_table.sql instead.

In any case, the result of all this is that I now cannot move beyond the character select screen. Does anyone have any suggestions for a solution?

[vales]

You're updating it all wrong. The instructions are in the PEQ readme file in the order you need to source everything in. What it looks like you're doing is sourcing in the SVN files before sourcing in the database which is basically blanking out the tables in mysql.

Initial Setup:

1. Unpack peqdb_1129Revxxx.sql.gz using winrar, gzip, whatever you use.
2. At a MySQL command prompt or GUI like Navicat source peqdb_1129Revxxx.sql into your database.
3. Source in the file load_player.sql.
4. (Optional) If you wish to use the EQOffline system, source in load_bots.sql.

For information on creating a new database see the EQEmu forums: http://eqemulator.net


Update Setup:

1. (Optional) If using EQOffline, run the bot_npcs.bat file, or bot_npcs.sh if using Linux.
2. Unpack peqdb_1129Revxxx.sql.gz using winrar, gzip, whatever you use.
3. Source drop_system.sql.
4. Source the new peqdb_1129Revxxx.sql into your database.
5. (Optional) If using EQOffline, source bot_npcs.sql.
6. Enter the updates folder, read the readme.txt there and be sure to source in any updates since the last time you updated.

Just source in drop_system.sql from Step #3 under "Update Setup" and you should be fine.

[neiv2]

Just to clarify, I'm updating the server code for a custom database. Will your instructions overwrite the custom settings in my db?

[vales]

Most likely.

Best thing to do is make backups of your custom stuff then source them in after a fresh database install. Always, always, always have backups. Even if it was a small sql modification, it's just so much easier to adapt it to any database once you've got it installed.

Although I love George's tools, basic SQL knowledge is a must for cases like these as it makes your life so much easier in the long run. Just learn basic insert and replace functions for MYSQL and you should be good to go. Make sure you're not overwriting existing data either, or it can get ugly.

Good luck.

[neiv2]

Yeah, I probably should have left well enough alone and not updated the server code. Right now I just need to fix the "zone unavailable" error when I try to enter world from the character select screen. Any suggestions for what might be causing this?

[neiv2]

A actually did back up my db before messing with the server code. Are you saying that I can just do a fresh install of everything and then restore my backed-up sql file?

[xsbaden]

I am having the same issue.

I source peq922.sql first, then load_player.sql into an empty db.

I have all the map files downloaded correctly, under c:\eqemu\Maps

(not maps\maps)

I can see my server, but it is locked. I can get to the char screen, but wont launch further than that.

Any help would be much appreciated.

[trevius]

You will need to check your world/zone log files to see exactly what is causing the problem. If you see errors, try posting them here. Probably 99% of the time, issues like this are due to your database revision not matching the revision of source code or binaries you are using from the SVN. If your binaries are newer than the PEQ DB version you are using, you will need to run any required SQL updates as noted in the change log or as seen in the /utils/sql/svn folder for between the revision your database is up to the revision of code you are using. For example, if you were running revision 222 of the database from PEQ, and you were running revision 900 from the SVN, you would need to run all of the SQL updates listed in that folder from 223 to 900.