anyone else here experiencing problems after JEMH upgrade?

C_ Faysal
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.
January 29, 2013

just upgraded 1.2.79 to 1.3

The license is not valid for the following reasons:
  

                
* There was a SQL exception thrown by the Active Objects library:
Database:
	- name:MySQL
	- version:5.1.61-log
	- minor version:1
	- major version:5
Driver:
	- name:MySQL-AB JDBC Driver
	- version:mysql-connector-java-5.1.22 ( Revision: ${bzr.revision-id} )

java.sql.SQLException: Error on rename of './jira/#sql-7b8_18759' to
'./jira/AO_78C957_LDAPCONF' (errno: 150)

2 answers

1 accepted

0 votes
Answer accepted
Andy Brook [Plugin People]
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.
January 30, 2013

Yes, there is a problem with upgrades and mysql, the resolution is to drop a JEMH table that is actually empty (AO_78C957_LDAPCONF). This problem stops the AO database layer initialising, which pretty much stops everything working, documented on the Javahollic Wiki.

C_ Faysal
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.
January 30, 2013

yes dropping that table will resolve the issue...thanks andy

0 votes
C_ Faysal
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.
January 29, 2013

oh ok.

looks like it is db driver specific.

no problems upgrading on a postgresql jira instance....

Suggest an answer

Log in or Sign up to answer