Jump to content
  • 0

Realmd db_version mismatch


D Q

Question

2023-12-29 11:25:44 ERROR:The table `db_version` indicates that your [Realmd] database does not match the expected structure!
2023-12-29 11:25:44 ERROR:
2023-12-29 11:25:44 ERROR:  [A] You have database Version: 21
2023-12-29 11:25:44 ERROR:                      Structure: 2
2023-12-29 11:25:44 ERROR:                        Content: 1
2023-12-29 11:25:44 ERROR:                    Description: Add_field_comments
2023-12-29 11:25:44 ERROR:
2023-12-29 11:25:44 ERROR:  [B] The core needs database Version: 22
2023-12-29 11:25:44 ERROR:                            Structure: 1
2023-12-29 11:25:44 ERROR:                              Content: 1
2023-12-29 11:25:44 ERROR:                          Description: Release 22
2023-12-29 11:25:44 ERROR:
2023-12-29 11:25:44 ERROR:You must apply all updates after [A] to [B] to use MaNGOS with this database.
2023-12-29 11:25:44 ERROR:These updates are included in the database/Realmd/Updates folder.


I tried to apply the update, but it's "skipped"

mangos@mangos:~/mangos/one/db/database/Realm/Updates/Rel22$ mysql -u mangos -pmangos mangos_auth < Rel22_01_001_Release_22.sql
===== Status =====	=== Expected ===	===== Found Version =====
* UPDATE SKIPPED *	Rel21_04_001 - IS NOT APPLIED	21_2_1 - Add_field_comments


My "db_version"

 

MariaDB [mangos_auth]> SELECT * FROM db_version ORDER BY VERSION DESC, structure DESC, content DESC LIMIT 0,1
    -> ;
+---------+-----------+---------+--------------------+------------------------------------------+
| version | structure | content | description        | comment                                  |
+---------+-----------+---------+--------------------+------------------------------------------+
|      21 |         2 |       1 | Add_field_comments | Base Database from 20150409 to Rel21_2_1 |
+---------+-----------+---------+--------------------+------------------------------------------+

Please feel free to comment.

Link to comment
Share on other sites

6 answers to this question

Recommended Posts

  • 0
    -- Evaluate all settings
    SET @cCurResult := (SELECT description FROM db_version ORDER BY `version` DESC, STRUCTURE DESC, CONTENT DESC LIMIT 0,1);
    SET @cOldResult := (SELECT description FROM db_version WHERE `version`=@cOldVersion AND `structure`=@cOldStructure AND `content`=@cOldContent);
    SET @cNewResult := (SELECT description FROM db_version WHERE `version`=@cNewVersion AND `structure`=@cNewStructure AND `content`=@cNewContent);

    IF (@cCurResult = @cOldResult) THEN    -- Does the current version match the expected version
        -- APPLY UPDATE

After reading the update file "Rel22_01_001_Release_22.sql", it's skipped because the current version "21_2_1" does not match the expected "21_4_1".
But how do I find the patch from "21_2_1" to "21_4_1"? The content in Rel21 doesn't look right :( :
 

ls Rel21
Rel20_to_BaseRel21_Updates  readme.txt

 

Edited by Dick Q
Link to comment
Share on other sites

  • 0

Good morning!

I've seen this issue come up a few times in the past. 

It looks like the updates have all been applied to the database, but the db_version hasn't been updated.

Use the following command in your MariaDB:

```
INSERT INTO db_version (version, `structure`, content, description, comment) VALUES(22, 1, 1, 'Release 22', 'Release 22');
```

 

Then you could be good to go.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy Terms of Use