org.springframework.dao.InvalidDataAccessResourceUsageException: could not execute statement; SQL [n/a]; nested exception is org.hibernate.exception.SQLGrammarException: could not execute statement
at org.springframework.orm.hibernate5.SessionFactoryUtils.convertHibernateAccessException(SessionFactoryUtils.java:228)
caused by: org.hibernate.exception.SQLGrammarException: could not execute statement
at org.hibernate.exception.internal.SQLExceptionTypeDelegate.convert(SQLExceptionTypeDelegate.java:63)
caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Table 'confluence.cwd_application_attribute' doesn't exist
at jdk.internal.reflect.GeneratedConstructorAccessor307.newInstance(Unknown Source)
Hi Russell,
welcome to the Atlassian Community!
The error message suggests not all needed tables could be created. Please kindly check if permissions on the database are set in a way the installer can create and populate them all.
For this I'd like to refer you to the documentation:
https://confluence.atlassian.com/doc/database-setup-for-mysql-128747.html
Please also pay special attention to the collation. The error message you have encountered was reported by other users of Community caused by a faulty collation. Please double check.
Cheers,
Daniel
Daniel,
Thanks for the info! I did follow the steps in the article you referenced and still no luck. It seems like not all the tables are being created during the setup process. Any thoughts as to why that might be given I have the MYSQL config setup correctly?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
From the outside this is very hard to tell. It is always a lot easier when sitting directly in front of the troubling system.
Apart from checking the collation, the setup itself and going through logs for (possibly) more information there is not much I could imagine doing from here right now.
Probably other Community members have additional information.
In case you are not bound to MySQL some users had a more positive experience using PostgreSQL as a backend - but I am aware this is not a fix of your problems. So in case you must go with MySQL I'd check in your case if other members come up with additional ideas here.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.