Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Confluence upgrade leaves me with missing tables

Benjamin Golba September 3, 2013

Hi!

I just made an attempt at updating Confluence (5.1.1 -> 5.2.3). The installation went OK and Confluence starts up. However, it doesn't work. Heres the error:

org.springframework.jdbc.BadSqlGrammarException: Hibernate operation: Could not execute query; bad SQL grammar []; nested exception is com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Table 'confluence.user_mapping' doesn't exist
	org.springframework.jdbc.support.SQLStateSQLExceptionTranslator.doTranslate(SQLStateSQLExceptionTranslator.java:97)
	org.springframework.jdbc.support.AbstractFallbackSQLExceptionTranslator.translate(AbstractFallbackSQLExceptionTranslator.java:72)

And so on...

I would like some advice on how to solve this.

Sincerely,

Benjamin

6 answers

1 vote
Alex Escalante September 26, 2013

Benjamin,

I had the same exception as you when I attempted to upgrade from 5.1.1 to 5.2.5. Following Septa's link(CONF-30380), and using workaround 2, while none of my tables returned any non-utf8 tables, I still performed the "utf8-bin" collate change. That seemed to do the trick, oddly enough. I hope you have the same success as I did.

Benjamin Golba September 26, 2013

Thanks for the tip Alex, I really appreciate it. Yeah, I had the same "issue" where none of the querys returned any result. I guess that fooled me to not go any further. I'll definately give it a another shot.

0 votes
Akeles
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 10, 2013

Yup. The workaround 2 in the https://jira.atlassian.com/browse/CONF-30380 did the trick!

0 votes
Benjamin Golba September 22, 2013

I was not able to update the system, though I was successful in recovering back to an older version. I did that by uninstalling v5.3.2 and copying the backup folders to the correct place, and then install the version I had previously.

0 votes
jmitchell@digby.com
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
September 5, 2013

Any further information here? confluence.user_mapping doesn't exist. Our system is dead in the water.

The steps in CONF-30380 don't seem to apply as all the tables in the system are InnoDB and have proper collation on them.

0 votes
Jens Collin
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
September 5, 2013

I appreciate the effort, it didn't solve anything for me though. I dont have time to work on an upgrade now so I'm reverting back to 5.1.5 and leaving it at that for a while. Thanks!

0 votes
Septa Cahyadiputra
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 3, 2013

Hi Benjamin,

By default, the latest release of Confluence should have the mentioned database. In total it should have 65 tables. You might want to access Confluence database and execute this query:

SHOW Tables;

If the above table is indeed not existed, I highly recommend you to roll back your database to pre-upgrade state and try to upgrade again. If it is created using a different case, you might want to change your database to be table name case insensitive to resolve the issue.

If the issue keep on occurring after several upgrade try, please contact our support channel and attach your atlassian-confluence.log which is located in <CONF_HOME_DIR>/logs/ that recorded the upgrade process.

Hope it helps.

Cheers,
Septa Cahyadiputra

Septa Cahyadiputra
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 3, 2013

Try to review this bug report as well as it could be related to your issue:

https://jira.atlassian.com/browse/CONF-30380

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events