# Running console doctrine:schema:update --force brings up errors

**URL:** <https://forum.mautic.org/t/running-console-doctrineupdate-force-brings-up-errors/15873>\
**Category:** Product Support\
**Created:** [August 30, 2020, 5:29pm UTC](https://forum.mautic.org/t/running-console-doctrineupdate-force-brings-up-errors/15873 "2020-08-30T17:29:54Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![simonjparker](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/simonjparker/32/1309_2.png) [@simonjparker](https://forum.mautic.org/u/simonjparker)\
**Post date:** [August 30, 2020, 5:29pm UTC](https://forum.mautic.org/t/running-console-doctrineupdate-force-brings-up-errors/15873/1 "2020-08-30T17:29:54Z")

</div>

**Your software**  
My Mautic version is: 3.1  
My PHP version is: 7.3

**Your problem**  
My problem is: I’ve updated to 3.0, and then 3.1 using the method outlined here - [https://mauteam.org/mautic/mautic-admins/mautic-update-how-to-dont-click-that-button/](https://mauteam.org/mautic/mautic-admins/mautic-update-how-to-dont-click-that-button/)

But running console doctrine:schema:update --force seems to bring up errors:

 ![Annotation 2020-08-30 182837](https://us1.discourse-cdn.com/flex020/uploads/mautic/original/2X/d/d8d3ded5f082da411f9092b2f0dcd7c95951d6a3.png)

Prior to this I ran console doctrine:migration:migrate and got:

 ![Annotation 2020-08-30 182613](https://us1.discourse-cdn.com/flex020/uploads/mautic/original/2X/5/5adef1bc5b046241f4727ac4b215ae5fe961677c.png)

I’ve still managed to update successfully, but I am concerned some of the DB specific stuff isn’t executing correctly.

Any advice would be much appreciated!

Thanks,

---

<div class="post-metadata">

**Author:** ![codes9](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/codes9/32/682_2.png) [@codes9](https://forum.mautic.org/u/codes9)\
**Post date:** [November 1, 2020, 1:31am UTC](https://forum.mautic.org/t/running-console-doctrineupdate-force-brings-up-errors/15873/2 "2020-11-01T01:31:19Z")

</div>

Did you run the migration and migration with --force before and after you updated?

If you get stuck restore from a backup and run these steps through slowly. If your database migration fails your Mautic install will do very unexpected things like run into random and weird errors. So it’s crucial that the migration succeeds before you call the upgrade good.

---

<div class="post-metadata">

**Author:** ![EJL](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/ejl/32/12155_2.png) [@EJL](https://forum.mautic.org/u/EJL)\
**Post date:** [November 1, 2020, 3:05pm UTC](https://forum.mautic.org/t/running-console-doctrineupdate-force-brings-up-errors/15873/3 "2020-11-01T15:05:41Z")

</div>

If you use the **mautic:update:find , mautic:update:apply and mautic:update:apply --finish** there is no need to manually run the schema update. @Yosu_Cadilla is no doubt an expert and I don’t speak for him, but I believe that post is most relevant when updating from Mautic 2.x to Mautic 3.x not necessarily from Mautic 3.x to 3.x. Hopefully he will chime in and clarify.

---

<div class="post-metadata">

**Author:** ![Yosu\_Cadilla](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/yosu_cadilla/32/6206_2.png) [@Yosu\_Cadilla](https://forum.mautic.org/u/Yosu_Cadilla)\
**Post date:** [November 1, 2020, 6:00pm UTC](https://forum.mautic.org/t/running-console-doctrineupdate-force-brings-up-errors/15873/4 "2020-11-01T18:00:10Z")

</div>

Hi guys,

That guide on my blog is in fact meant for M2 to M2 upgrades and has not been tested with M2 to M3 upgrades.

Please keep in mind that for upgrading from M2 to M3 you need to first upgrade to 2.16.3 before you do the jump.

I’ve been working on an M2 to M3 upgrade guide for a while, hope I’ll be able to publish it soon enough…