cancel
Showing results for 
Search instead for 
Did you mean: 

Problem migrating form 2.0 to 2.1 with Mysql on linux

jey
Champ in-the-making
Champ in-the-making
Hi,

I have notice some kind of a bug during the database schema update.

I have two environment: one on linux (SLES) and the other on windows xp.
Both use mysql.


On my windows environment the migration worked fine.

On my linux environment, tables related to JBPM add been created in uppercase in mysql, and the schema update script is looking for lowercase table names!
So the update failed!

For information: on my windows environment all the table had been created in lowercase!

SO I have try to modify all the table in uppercase to lowercase ! Long work … But it still doesn't work ! Now there is issues with the column names….

This is quite disturbing !!!"SO I reverted to my last backup and I am still using version 2.0

Should I raise an issue in JIRA or anyone can tell me where does this error comes from and how to solve it? (I am affraid of having many issue if I just try to change all cases).

Regards,
Jey.
20 REPLIES 20

davidc
Star Contributor
Star Contributor
This has been fixed on HEAD.

jey
Champ in-the-making
Champ in-the-making
Ok I'll check this out.

Thanks for your reply  !

jey
Champ in-the-making
Champ in-the-making
Ok I have try the head version alfresco-community-war-2.1.0R2-dev.tar.gz

There is no more error with the table name !!!

Fine, but now I have the following issue:

com.mysql.jdbc.exceptions.MySQLSyntaxErrorException: Unknown column 'ISASYNCEXCL__' in 'field list'

There is also a problem of case with the colum name I guess …

😞

jey
Champ in-the-making
Champ in-the-making
Looking into the script I saw the following line:

UPDATE JBPM_NODE SET ISASYNCEXCL__ = 0;

in the file:

AlfrescoSchemaUpdate-2.1-JBPMData.sql

But the problem is that in the database, the table JBPM_NODE contains a field named ISASYNC_ but no field ISASYNCEXCL_

davidc
Star Contributor
Star Contributor
Odd, I have that column in my install.  I'll diagnose further.

schneika
Champ in-the-making
Champ in-the-making
Please can you post the Download-URL for the HEAD-Developer-Versions of the war-File.

jey
Champ in-the-making
Champ in-the-making
Hi again david,

Pleae help me !!! I am about to throw my laptop over the window ! Hopefully we can't open windows in this building :-). I am safe.

I stop joking ….

I have check out the colum of my two bases: windows one and linux (sles10) one and they are quite different …

My two alfresco were install with the bundle version installer 2.0 (windows and linux ones). So they must use the same war file, so the must have deploy the same database schema …

But they are differents… which is quite disturbing …. :?

Here is my windows database column of the table jbpm_node
ID_
CLASS_
NAME_
PROCESSDEFINITION_
ISASYNC_
ACTION_
SUPERSTATE_
SUBPROCESSDEFINITION_
DECISIONEXPRESSION_
DECISIONDELEGATION
SIGNAL_
CREATETASKS_
ENDTASKS_
NODECOLLECTIONINDEX_
DESCRIPTION_
ISASYNCEXCL_
SUBPROCNAME_
SCRIPT_

Here is the linux one:
ID_
CLASS_
NAME_
PROCESSDEFINITION_
ISASYNC_
ACTION_
SUPERSTATE_
SUBPROCESSDEFINITION_
DECISIONEXPRESSION_
DECISIONDELEGATION
SIGNAL_
CREATETASKS_
ENDTASKS_
NODECOLLECTIONINDEX_

I know it seems that I have forgot a part, but I promise not Smiley Very Happy … The table looks like this!

I hope you'll find the origin of the issue!

I am expecting for the next head release!

Thanks for all your work…

Just want to tell you that this issue excluded, the version 2.1 is great, on windows in deed 🙂

Regards,
jey

davidc
Star Contributor
Star Contributor
There have been a few issues found with the upgrade on oracle.  Some more fixes have gone in today.  In particular, there's an extra _ in the update sql statement that shouldn't be there.

Can you just clarify that in both cases, you previously installed with 2.0 and are now upgrading to 2.1.