Updated today and have naked char's :-)
 

So I updated the DB and Source today to peqdb version 610 and the code to r666. Everything compiled fine and had no problems. I sourced the various sql files from the utils directory.

600_group_leadership.sql
612_instance_changes.sql
615_adventure_assassination.sql
619_Adventure_Recruiter_Flavor.sql
621_LDoNTraps.sql
633_ucs.sql
634_TrapTemplateDefaultValue.sql
643_BotsTable.sql
646_archery_penalty_rule.sql
665_heroic_resists.sql

I also added in the SQL updates from the new db version.

Rev553.sql
Rev590.sql
Rev59.sql
Rev610.sql

The problem is whenever I logon with either Titanium or SoF all of my characters are naked. When I look in database all of the items appear to be in palce still. I did backup the tables before I loaded the changes. Here are the errors being dropped into the log when I log a character on to the server.

If anayone has any suggestions I would love to hear them. I am hoping I don't have to rebuild all of the inventories. :-( (couple hundred characters are created on the server, shudder)

It sounds like your items table is empty or not up to date.

Why did you update to 610 and then "back-patch" 590, 600?
What rev did you start with?

I'm hoping you didn't do these in the order you listed.

also Rev59.sql shouldn't have even been an option.

Did you use the full peqdb file? (ie peqdb_1129rev628.sql?)

Do you have customizations to the items db or spawns? if not, the easiest fix would be
source drop_system.sql
source peqdb_1129Rev628.sql

that will bring you to 628 (encompasses also up to 633_ucs.sql)

you can then source in anything above the 633_ucs.sql.

Rev59.sql was a typo from when I pasted out of the dir listing. Sorry about that. I was not sourced.

The items table is populated and has all of the data. I dod not source the entire database, I have some customizations, but I can add those back in easy enough if I have to, I am trying to avoid that though. If that is my only option then I will pull the trigger. Not sure why the sourcing of the sql's did not work if I have to reload the entire DB.

I was on the 553 version of the DB prior to my upgrade today. So I sourced everything after 553.

Your original custom DB should work just fine as long as you source in the SQL from the /utils/sql/svn directory in the EQEmu source code trunk. The most important one is the one for Heroic Resists. Make sure that you ran that SQL AFTER you did all of the PEQ db update stuff, or you will be missing those new fields, which will cause items to fail to load, which is what is causing your problem. Your inventory table should be fine.

I assumed after reading these that something got corrupted during my upgrade. So I decided to start again. I ran drop_system.sql and reloaded the database. I sourced in all the updates that were later than the 628 version of the db.

I restarted my world and logged back in and I am still naked. :-(

I sourced in the SQL updates and the SQL updates from the EQEmu.

Check your items table and be sure that you have fields near the far right end of the table that are named; herioc_pr, heroic_dr, heroic_fr, heroic_cr, and heroic_svcorrup. If you don't have those fields, then the way you are running the SQL updates is being done in the wrong order. You MUST run the heroic resists sql update from the EQEmu folder after you are done with everything else. Otherwise, you are overwritting the update by resourcing the PEQ stuff. This is because redoing the database from scratch will remove all tables and then re-add them, which removes the new columns you just added.

I am having the same problem and I have confirmed the heroic resists fields are in the items table. I am on peqdb 669 and eqemu rev 670.

Since I run 64bit, I'm building 32bit version to make sure it doesn't have to do with my arch. I'll post again when I've tested that.

The 32bit compile does not have the same problem for me. I'll look into the changes to see where the problem for 64bit is.

Make sure you do a make clean, your library HAS to be rebuilt in order to accept the changes to the items table.

Hrm. I doubt I did a make clean. Are the dependencies incorrect so it won't rebuild the library?

I'm doing a make clean and rebuilding to test.

Yup, make clean before building took care of it. Stupid dependencies... (mutter grumble).

make clean fixed my inventory problem as well. Thank you! One more thing I have learned. :-)

However, I have a new problem. I cannot cast any spells. I get an Arguement out of range when I try to cast a spell. It gives me that error if I try to cast a spell from my spell gem, or if I try to use the #castspell command as well.

Any thoughts for this one?

I had the same problem, try:

Or, just grab the newest PEQ database and use that spells_new table.

I tried both solutions, I tried entering the SQL to update the table, problem still existed.

I then did another drop_system.sql and sourced in the 669 version of the database.

I am still getting these messages in game.

You say, '#castspell 278'
Error: #castspell: Arguement out of range

Beginning to memorize Spikecoat...
Unexpected error: spell id out of range

Try using #findspell - see if it says spells not loaded.