Your database appears to need patching to a higher level. See Tools->Server Informati

Hello Guys
I need to resolve this issue

Your database appears to need patching to a higher level. See Tools->Server Information to review patch levels.

my sql DataBase is in 1.3.8
but the software is on 1.3.9

Zen Cart 1.3.9b
Database Patch Level: 1.3.8

:yes:........Please help............:bigups:

I need to know this too. I don't know where to go to patch my database.

If you did not run the Upgrade on the database then it will still be v1.3.8 even if you have the code as v1.3.9 ... :unsure:

I just updated to 1.3.9d and I am getting that message and how do I update the database so this message goes away?

I also got the same problem...please help us :cry:

Try this:
www.your_web_site.com/zc_install

1. when you accept the agreement on the next page you will notice at the bottom to Update Database
2. So click on this:
3. Click the tick box at the bottom to which version you are upgrading to..
4. Then upgrade...

@ karazy and mydreams

Folks, please carefully read the upgrade instructions, changelog and whatsnew files contained in the docs folder of the package, it will save you a lot of headaches if you follow these instructions step by step and to a tee :yes:

dear haredo,

i've tried the step but still got problem

"ATTENTION: Problems Found

* NOTE: Skipped upgrade statements: 3
  See details at bottom of page for your inspection.
  (Details also logged in the "upgrade_exceptions" table.)"

Still facing the problem.....please help... :cry:

so, anybody fixed this problem...? can share how to do..? thanks in advance....

I think I read the upgrade instructions pretty carefully, but obviously I missed something.

This is what my new shop currently looks like:
http://pocketcarnival.com.au/demo/

And it has that same error:
Your database appears to need patching to a higher level. See Admin->Tools->Server Information to review patch levels.

I installed Zen Cart 1.3.9e today, and then imported my database from my current shop (1.3.8).

Is this incorrect?

Oh, err... I just did what this thread says:

http://www.zen-cart.com/forum/showthread.php?t=155175&highlight=database+patching

Yay!

Trying to upgrade my database and when I click the upgrade database I get the following message:

1253 COLLATION 'latin1_general_ci' is not valid for CHARACTER SET 'utf8'
in:
[CREATE TABLE zen_counter_history_clean as SELECT * FROM zen_counter_history WHERE 1 GROUP BY startdate COLLATE latin1_general_ci;]

Someone said in another post I need to edit the sql update but how do I do that exactly?

Hello,

I'm afraid I need help with this too. I have read loads of posts and docs, but I just need to clarify the process.

I have an old zenCart installation version 1.3.8a

I have moved it to a new version 1.3.9d

it all looks fine except for the database patch message.

Do I need to do the following?

1 update the old version to 1.3.9f then export the database

2 update or even delete and do a new manual install of 1.3.8f on the new server

3 import the updated database to the new 1.3.9f installation

It all seems a bit scary and i don't want to break the old installation, please help :unsure:
thanks

Hey guys i think most of you who had database problems have upgraded to the new version using initially your old database. You should use a new/fresh database if you do full upgrade, then just restore the old database by overwriting the new one.

Anyway its not yet too late as long as you have a copy of your unaltered old database.

Here's what you might do:

1. Create backup of the old database
   mysqldump -u [user] -p OldDbName > OldDbBackup.sql
   (Then enter [user] password if prompted..)
2. Restore it to the new one
   mysql -u [user] -p OldDbBackup.sql > NewDbName

castlino,

1. Most people have no access to command-line, so cannot do what you're suggesting ... and most would have no clue what you're even suggesting, and shouldn't even try.
   And those who do know what you're talking about have probably already done their upgrade without difficulty.

2. There's nothing wrong with upgrading the original database directly (after first doing a test upgrade in a separate database first to make sure everything works fine there before touching the live site).

3. What you're talking about seems to be very narrow-scoped in its context and doesn't take into account the big picture of what "most of you who had database problems" are all experiencing.

Please excuse me if I sound rude or offensive: I don't mean to be.
I just think your post would be confusing to most people, and that if they find it confusing then they should ignore it.