# SQL error on upgrade from v2 to v3

**URL:** <https://forum.ghost.org/t/sql-error-on-upgrade-from-v2-to-v3/11907>\
**Category:** Installation\
**Created:** [February 10, 2020, 2:39pm UTC](https://forum.ghost.org/t/sql-error-on-upgrade-from-v2-to-v3/11907 "2020-02-10T14:39:52Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Bapf](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/bapf/32/6291_2.png) [@Bapf](https://forum.ghost.org/u/Bapf)\
**Post date:** [February 10, 2020, 2:39pm UTC](https://forum.ghost.org/t/sql-error-on-upgrade-from-v2-to-v3/11907/1 "2020-02-10T14:39:52Z")

</div>

I admittedly haven’t upgraded my ghost installation for far to long. A shortfall I wanted to fix just now.

So I upgraded ghost-cli with npm and afterwards wanted to upgrade my 2.0.2 installation (which initially startet as a 1.x installation) to 3.5.1, which gives me the following error:

Message: show columns from `members_stripe_customers_subscriptions` - ER\_NO\_SUCH\_TABLE: Table ‘ghost.members\_stripe\_customers\_subscriptions’ doesn’t exist  
Suggestion: journalctl -u ghost\_localhost -n 50

Debug Information:  
OS: Ubuntu, v16.04.6 LTS  
Node Version: v12.15.0  
Ghost Version: 3.5.1  
Ghost-CLI Version: 1.13.1  
Environment: production  
Command: ‘ghost update --force’

Is there any way to create this table beforhand or instruct the update process to create it?

thx,  
Bapf

---

<div class="post-metadata">

**Author:** ![ellotheth](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/ellotheth/32/6329_2.png) [@ellotheth](https://forum.ghost.org/u/ellotheth)\
**Post date:** [February 13, 2020, 12:35pm UTC](https://forum.ghost.org/t/sql-error-on-upgrade-from-v2-to-v3/11907/2 "2020-02-13T12:35:54Z")

</div>

I had the same error upgrading from 1.26.2 to 3.5.2:

```auto
Debug Information:
    OS: Debian GNU/Linux, v8
    Node Version: v10.19.0
    Ghost Version: 3.5.2
    Ghost-CLI Version: 1.13.1
    Environment: production
    Command: 'ghost upgrade v3'
Message: show columns from `members_stripe_customers_subscriptions` - ER_NO_SUCH_TABLE: Table 'wonderblog_new.members_stripe_customers_subscriptions' doesn't exist
Suggestion: journalctl -u ghost_wonderproxy-com -n 50
Stack: Error: show columns from `members_stripe_customers_subscriptions` - ER_NO_SUCH_TABLE: Table 'wonderblog_new.members_stripe_customers_subscriptions' doesn't exist
    at Server.server.close (/usr/lib/node_modules/ghost-cli/lib/utils/port-polling.js:38:28)
    at Object.onceWrapper (events.js:286:20)
    at Server.emit (events.js:198:13)
    at emitCloseNT (net.js:1619:8)
    at process._tickCallback (internal/process/next_tick.js:63:19)

```

Upgrading to 3.4 with `ghost upgrade 3.4.0` worked fine.

---

<div class="post-metadata">

**Author:** ![Bapf](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/bapf/32/6291_2.png) [@Bapf](https://forum.ghost.org/u/Bapf)\
**Post date:** [February 13, 2020, 2:20pm UTC](https://forum.ghost.org/t/sql-error-on-upgrade-from-v2-to-v3/11907/3 "2020-02-13T14:20:38Z")

</div>

thx, worked!

I already tried updating to an not so recent version, but I didn’t catch that I had to use “upgrade” instead of “update” for that. ☹

---

<div class="post-metadata">

**Author:** ![keking](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/keking/32/6335_2.png) [@keking](https://forum.ghost.org/u/keking)\
**Post date:** [February 13, 2020, 3:29pm UTC](https://forum.ghost.org/t/sql-error-on-upgrade-from-v2-to-v3/11907/4 "2020-02-13T15:29:05Z")

</div>

I have this same error about stripe customer subscriptions, but when I try to upgrade to 3.4.0 it says I’m already at 3.5.x. Is there anyway to rollback that I haven’t found?

---

<div class="post-metadata">

**Author:** ![Bapf](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/bapf/32/6291_2.png) [@Bapf](https://forum.ghost.org/u/Bapf)\
**Post date:** [February 13, 2020, 3:58pm UTC](https://forum.ghost.org/t/sql-error-on-upgrade-from-v2-to-v3/11907/5 "2020-02-13T15:58:14Z")

</div>

ghost update --rollback  
should do the trick