# Mongodb - not valid database version **URL:** \ **Category:** Report a Bug\ **Created:** [April 10, 2024, 12:57pm UTC](https://community.datagerry.com/t/mongodb-not-valid-database-version/576 "2024-04-10T12:57:58Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![marcinw](https://avatars.discourse-cdn.com/v4/letter/m/eb8c5e/32.png) [@marcinw](https://community.datagerry.com/u/marcinw)\ **Post date:** [April 10, 2024, 12:57pm UTC](https://community.datagerry.com/t/mongodb-not-valid-database-version/576/1 "2024-04-10T12:57:58Z")
Hello, When i opened application logs after upgrade to 2.1.0 version i saw strange communicates. > **Log content** > > [2024-04-10 14:36:09][ERROR] — > There are new updates available. Updating initialised… > Current Updater Version: 20200512 > Newest Update Version: 20200513 > ( **check**.py) > [2024-04-10 14:36:09][WARNING] — The current database version does not match the valid database version. ( **check**.py) my database have version: ```auto db.adminCommand( { getParameter: 1 , featureCompatibilityVersion: 1 } ) { featureCompatibilityVersion: { version: '6.0' }, ok: 1 } ``` and you wrote in subject [DATAGERRY 2.1.0 released](https://community.datagerry.com/t/datagerry-2-1-0-released/567/1) in Announcements that you support version 6.0 > [@DATAGERRY 2.1.0 released](https://community.datagerry.com/t/datagerry-2-1-0-released/567/1): > > The version of MongoDB for development is increased to 6.0 due the upcoming End of Life for MongoDB 4.4 and 5.0. There are currently no issues with MongoDB 4.4 and 5.0 and they should be compatible with the newest Version of DATAGERRY. Why i saw that announcement? ---
**Author:** ![adnan.smajic](https://dub1.discourse-cdn.com/flex013/user_avatar/community.datagerry.com/adnan.smajic/32/754_2.png) [@adnan.smajic](https://community.datagerry.com/u/adnan.smajic)\ **Post date:** [April 10, 2024, 1:13pm UTC](https://community.datagerry.com/t/mongodb-not-valid-database-version/576/2 "2024-04-10T13:13:41Z")
Hi @marcinw , this is an update from DATAGERRY, which updates the types with new properties so that they are compatible with the new version of DATAGERRY, it has nothing to do with MongoDB itself. Your types should all have now the two additional properties after the update: - ‘global\_template\_ids’ - ‘selectable\_as\_parent’ ---
**Author:** ![marcinw](https://avatars.discourse-cdn.com/v4/letter/m/eb8c5e/32.png) [@marcinw](https://community.datagerry.com/u/marcinw)\ **Post date:** [April 12, 2024, 9:53am UTC](https://community.datagerry.com/t/mongodb-not-valid-database-version/576/3 "2024-04-12T09:53:41Z")
> [@marcinw](#): > > [2024-04-10 14:36:09][WARNING] — The current database version does not match the valid database version. ( **check**.py) Ok for first line where is error i undestand but for second line where is warning what is meaning: `[2024-04-10 14:36:09][WARNING] — The current database version does not match the valid database version. ( **check**.py)` ? ---
**Author:** ![adnan.smajic](https://dub1.discourse-cdn.com/flex013/user_avatar/community.datagerry.com/adnan.smajic/32/754_2.png) [@adnan.smajic](https://community.datagerry.com/u/adnan.smajic)\ **Post date:** [April 12, 2024, 10:57am UTC](https://community.datagerry.com/t/mongodb-not-valid-database-version/576/4 "2024-04-12T10:57:49Z")
Hi @marcinw , in your initial Message you had this log entry: Current Updater Version: 20200512 Newest Update Version: 20200513 Your Types and Objects in DATAGERRY had the SCHEMA of the the Version 20200512. In the newest version we needed to extend the Schema by adding new fields ( \* ‘global\_template\_ids’ and ‘selectable\_as\_parent’). Therefore we wrote an Update which will automatically update the Types and Objects to the required version (20200513). So Datagerry was just checking for the version of the objects and then installed the new version to be compatible with the newest update. It says invalid just because it found version number ‘20200512’ saved as a value in MongoDB but the newest version is ‘20200513’. BR Adnan ---
**Author:** ![marcinw](https://avatars.discourse-cdn.com/v4/letter/m/eb8c5e/32.png) [@marcinw](https://community.datagerry.com/u/marcinw)\ **Post date:** [April 19, 2024, 5:47am UTC](https://community.datagerry.com/t/mongodb-not-valid-database-version/576/5 "2024-04-19T05:47:11Z")
Ok, thanks for the explanation 🙂 ---
**Author:** ![sink1](https://dub1.discourse-cdn.com/flex013/user_avatar/community.datagerry.com/sink1/32/790_2.png) [@sink1](https://community.datagerry.com/u/sink1)\ **Post date:** [April 19, 2024, 11:02am UTC](https://community.datagerry.com/t/mongodb-not-valid-database-version/576/6 "2024-04-19T11:02:52Z")
> [@adnan.smajic](#): > > So Datagerry was **just checking** for the version of the objects and then installed the new version to be compatible with the newest update. Does this mean that it will still work? “Just checking” is meant to convey a friendly, no-pressure tone, to encourage a response. It ought to imply that datagerry would carry on working. Will datagerry carry working even after mentioning the database version? ---
**Author:** ![adnan.smajic](https://dub1.discourse-cdn.com/flex013/user_avatar/community.datagerry.com/adnan.smajic/32/754_2.png) [@adnan.smajic](https://community.datagerry.com/u/adnan.smajic)\ **Post date:** [April 19, 2024, 1:34pm UTC](https://community.datagerry.com/t/mongodb-not-valid-database-version/576/7 "2024-04-19T13:34:44Z")
Hi @sink1 , Yeah everything is fine, this is a planned update. To prevent future confusion with these messages we will update the message text for future releases :). BR Adnan ---
**Author:** ![adnan.smajic](https://dub1.discourse-cdn.com/flex013/user_avatar/community.datagerry.com/adnan.smajic/32/754_2.png) [@adnan.smajic](https://community.datagerry.com/u/adnan.smajic)\ **Post date:** [April 4, 2025, 8:11am UTC](https://community.datagerry.com/t/mongodb-not-valid-database-version/576/8 "2025-04-04T08:11:00Z")