Upgrade from 3.5.17 to 5.0.3 issue

Question

Hi all,

Just performed upgrade from 3.5.17 to 5.0.3 (manually).

Based on the logs, encountered an error while pointing 5.0.3 application to database:

1.)

caused by: org.springframework.jdbc.BadSqlGrammarException: Hibernate operation: Could not execute query; bad SQL grammar []; nested exception is java.sql.SQLSyntaxErrorException: ORA-00904: "SPACE0_"."SPACESTATUS": invalid identifier

at org.springframework.jdbc.support.SQLStateSQLExceptionTranslator.doTranslate(SQLStateSQLExceptionTranslator.java:97)
caused by: java.sql.SQLSyntaxErrorException: ORA-00904: "SPACE0_"."SPACESTATUS": invalid identifier

at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:447)

2.)

2014-09-01 15:57:11,649 ERROR [http-8081-3] [[Standalone].[localhost].[/].[file-server]] log Servlet.service() for servlet file-server threw exception
org.springframework.jdbc.BadSqlGrammarException: Hibernate operation: could not load: [com.atlassian.confluence.core.ContentEntityObject#51905073]; bad SQL grammar []; nested exception is java.sql.SQLSyntaxErrorException: ORA-00904: "CONTENTENT1_"."PLUGINVER": invalid identifier

What should I do regarding the errors that I encountered?

Thanks in advace.

HANSHIN · Answer

Hi Septa,
My apologies for the late reply.
Btw, thanks to your reply I performed my upgrade from v3.5.17 to v5.0.3 successfully.

But when I tried upgrading to v5.0.3 to v5.5.2,
I encountered this error:
Table 'LINKS' has more than one primary key

I tried again to apply the solution that you said but to no avail the error still occurs and the upgrade is not successful.

What should I do?

Thanks in advance.

Septa Cahyadiputra · Answer

Hi Hanshin,

This issue could be related with a bug mentioned here: https://jira.atlassian.com/browse/CONF-31333

Please try the mentioned knowledge base and see how it goes:

https://confluence.atlassian.com/pages/viewpage.action?pageId=419004803

Also make sure that your license is valid and applicable for 5.0.3. If the above information doesn't help, we highly recommend you to contact our support team through https://support.atlassian.com/to further investigate your issue by reviewing your complete log confidentially.

Hope it helps.

Cheers,
Septa Cahyadiputra