topic Re: Problem migrating form 2.0 to 2.1 with Mysql on linux in Alfresco Archive

Problem migrating form 2.0 to 2.1 with Mysql on linux

jey — Thu, 05 Jul 2007 08:11:32 GMT

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

Re: Problem migrating form 2.0 to 2.1 with Mysql on linux

davidc — Thu, 05 Jul 2007 08:23:38 GMT

This has been fixed on HEAD.

Re: Problem migrating form 2.0 to 2.1 with Mysql on linux

jey — Thu, 05 Jul 2007 08:59:39 GMT

Ok I'll check this out.

Thanks for your reply !

Re: Problem migrating form 2.0 to 2.1 with Mysql on linux

jey — Thu, 05 Jul 2007 09:35:06 GMT

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 …

😞

Re: Problem migrating form 2.0 to 2.1 with Mysql on linux

jey — Thu, 05 Jul 2007 09:47:10 GMT

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_

Re: Problem migrating form 2.0 to 2.1 with Mysql on linux

davidc — Thu, 05 Jul 2007 10:04:14 GMT

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

Re: Problem migrating form 2.0 to 2.1 with Mysql on linux

schneika — Thu, 05 Jul 2007 10:16:33 GMT

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

Re: Problem migrating form 2.0 to 2.1 with Mysql on linux

jey — Thu, 05 Jul 2007 11:35:47 GMT

http://dev.alfresco.com/downloads/nightly/dist/alfresco-community-war-2.1.0R2-dev.zip

Re: Problem migrating form 2.0 to 2.1 with Mysql on linux

jey — Thu, 05 Jul 2007 16:19:22 GMT

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 … 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

Re: Problem migrating form 2.0 to 2.1 with Mysql on linux

davidc — Thu, 05 Jul 2007 16:56:00 GMT

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.

Re: Problem migrating form 2.0 to 2.1 with Mysql on linux

jey — Mon, 09 Jul 2007 09:51:32 GMT

Ok I had being saying something quite stupid.
My two database are the same…

I don't know why I could not see all the column on linux…

So know the schema update script is working fine.
The problem was the extra "_"

But now that this is solve, my Alfresco stay "freeze" to the following steps:
[org.alfresco.repo.admin.patch.PatchExecuter] Checking for patches to apply …

There is no error… But Alfresco doesn't start …

If you got any advices, please let me know

Regards,
jey.

Re: Problem migrating form 2.0 to 2.1 with Mysql on linux

lateral — Wed, 19 Sep 2007 02:29:52 GMT

I also have exactly this problem…upgrading a 2.0.1 Windows DM and WCM environment to 2.1 Enterprise. Copied the war across, rebuilt the indexes and now it hangs while checking for patches to apply…

thanks,
Alex

Re: Problem migrating form 2.0 to 2.1 with Mysql on linux

paulhh — Fri, 21 Sep 2007 14:33:23 GMT

Hi Alex

You should report this to Support since you're using Enterprise. Knowing exactly which versions would help (e.g. was it Community -> Enterprise). Also, knowing which DB is important, since not all DBs have been certified for 2.1E yet.

Cheers
Paul.

Re: Problem migrating form 2.0 to 2.1 with Mysql on linux

derek — Fri, 21 Sep 2007 14:33:59 GMT

How long has it been like that, and is the machine doing anything?

Re: Problem migrating form 2.0 to 2.1 with Mysql on linux

lateral — Wed, 03 Oct 2007 04:26:33 GMT

The environment is not in production, however it was trying to upgrade 2.01 Enterprise to 2.1 Enterprise using a HSQL database. Its a demo/sandbox environment to show conceptual ideas to a customer. Basically it seems that any upgrade of 2.0.1E to 2.1E complains of invalid indexes and forces an index rebuild…is this expected?

Re: Problem migrating form 2.0 to 2.1 with Mysql on linux

derek — Wed, 03 Oct 2007 09:47:23 GMT

Post the log, please.

Re: Problem migrating form 2.0 to 2.1 with Mysql on linux

lateral — Wed, 03 Oct 2007 23:50:47 GMT

09:40:04,847 WARN [org.springframework.remoting.rmi.RmiRegistryFactoryBean] Could not detect RMI registry - creating new one
09:40:10,492 INFO [org.alfresco.repo.domain.schema.SchemaBootstrap] Schema managed by database dialect org.hibernate.dialect.HSQLDialect.
09:40:10,492 INFO [org.alfresco.repo.domain.schema.SchemaBootstrap] Alfresco is using the HSQL default database. Please only use this while evaluating Alfresco, it is NOT recommended for production or deployment!
09:40:12,915 INFO [org.alfresco.repo.domain.schema.SchemaBootstrap] No changes were made to the schema.
09:40:19,764 WARN [org.alfresco.repo.admin.ConfigurationChecker] The Alfresco 'dir.root' property is set to a relative path './alf_data'. 'dir.root' should be overridden to point to a specific folder.
09:40:19,764 INFO [org.alfresco.repo.admin.ConfigurationChecker] The Alfresco root data directory ('dir.root') is: .\alf_data
09:40:20,514 INFO [org.alfresco.repo.admin.patch.PatchExecuter] Checking for patches to apply …

thats it …without any special debug settings…do you want me to try it with any special log settings? It just hangs at this point

Re: Problem migrating form 2.0 to 2.1 with Mysql on linux

lateral — Thu, 04 Oct 2007 01:02:29 GMT

hmm my bad…I"m just not patient enough !!

Patch updates completed at 10.56…so it took over 1hr to update the patches !

Is that normal?

Re: Problem migrating form 2.0 to 2.1 with Mysql on linux

derek — Thu, 04 Oct 2007 05:40:55 GMT

That depends on how much data you have and how HSQL performs. Which patches did it run?

Re: Problem migrating form 2.0 to 2.1 with Mysql on linux

lateral — Thu, 04 Oct 2007 06:05:51 GMT

ok…yeah i just tried it with a much smaller set of data and it ran in just 40 minutes

the patches it ran were:

09:40:20,514 INFO [org.alfresco.repo.admin.patch.PatchExecuter] Checking for patches to apply …
10:56:20,854 INFO [org.alfresco.repo.admin.patch.PatchExecuter]
=== Applied patch                 ===
ID: patch.AVMAspects
RESULT:
Aspects were moved.
=====================================
10:56:20,854 INFO [org.alfresco.repo.admin.patch.PatchExecuter]
=== Applied patch                 ===
ID: patch.AVMLayeredSnapshot
RESULT:
Layered Node indirectionVersions set.
=====================================
10:56:20,854 INFO [org.alfresco.repo.admin.patch.PatchExecuter]
=== Applied patch                 ===
ID: patch.AVMLocking
RESULT:
Necessary web projects added.
=====================================
10:56:20,854 INFO [org.alfresco.repo.admin.patch.PatchExecuter]
=== Applied patch                 ===
ID: patch.AVMProperties
RESULT:
Properties were moved.
=====================================
10:56:20,854 INFO [org.alfresco.repo.admin.patch.PatchExecuter]
=== Applied patch                 ===
ID: patch.ReadmeTemplate
RESULT:
Imported view into bootstrap location: /app:company_home/app:dictionary/app:content_templates (workspace://SpacesStore/a3e6de75-d730-11db-ba1c-95447b08afa4)
=====================================
10:56:20,854 INFO [org.alfresco.repo.admin.patch.PatchExecuter]
=== Applied patch                 ===
ID: patch.db-V2.1-ExplicitIndexes
RESULT:
Script completed
=====================================
10:56:20,854 INFO [org.alfresco.repo.admin.patch.PatchExecuter]
=== Applied patch                 ===
ID: patch.db-V2.1-FKIndexes
RESULT:
Script completed
=====================================
10:56:20,854 INFO [org.alfresco.repo.admin.patch.PatchExecuter]
=== Applied patch                 ===
ID: patch.db-V2.1-JBPMProcessKey
RESULT:
Script completed
=====================================
10:56:20,854 INFO [org.alfresco.repo.admin.patch.PatchExecuter]
=== Applied patch                 ===
ID: patch.db-V2.1-JBPMUpdate
RESULT:
Script completed
=====================================
10:56:20,854 INFO [org.alfresco.repo.admin.patch.PatchExecuter]
=== Applied patch                 ===
ID: patch.db-V2.1-NotNullColumns
RESULT:
Script completed
=====================================
10:56:20,854 INFO [org.alfresco.repo.admin.patch.PatchExecuter]
=== Applied patch                 ===
ID: patch.db-V2.1-RemoveWcmSubmittedAspect
RESULT:
Script completed
=====================================
10:56:20,854 INFO [org.alfresco.repo.admin.patch.PatchExecuter]
=== Applied patch                 ===
ID: patch.db-V2.1-VersionColumns2
RESULT:
Script completed
=====================================
10:56:20,854 INFO [org.alfresco.repo.admin.patch.PatchExecuter]
=== Applied patch                 ===
ID: patch.groupMembersAsIdentifiers
RESULT:
Reindexed usr:authorityContainer with identifiers
=====================================
10:56:20,854 INFO [org.alfresco.repo.admin.patch.PatchExecuter]
=== Applied patch                 ===
ID: patch.redeploySubmitProcess
RESULT:
Re-deployed 1 workflows.
=====================================
10:56:20,854 INFO [org.alfresco.repo.admin.patch.PatchExecuter]
=== Applied patch                 ===
ID: patch.versionHistoryPerformance
RESULT:
Updated 0 version history objects to improve performance.
=====================================
10:56:20,854 INFO [org.alfresco.repo.admin.patch.PatchExecuter]
=== Applied patch                 ===
ID: patch.webScriptsReadme
RESULT:
Imported view into bootstrap location: /app:company_home/app:dictionary (workspace://SpacesStore/a3e6de75-d730-11db-ba1c-95447b08afa4)
=====================================
10:56:20,854 INFO [org.alfresco.repo.admin.patch.PatchExecuter]
=== Applied patch                 ===
ID: patch.webscripts
RESULT:
Imported view into bootstrap location: /app:company_home/app:dictionary (workspace://SpacesStore/a3e6de75-d730-11db-ba1c-95447b08afa4)
=====================================
10:56:20,854 INFO [org.alfresco.repo.admin.patch.PatchExecuter]
=== Applied patch                 ===
ID: patch.webscripts2
RESULT:
Imported view into bootstrap location: /app:company_home/app:dictionary (workspace://SpacesStore/a3e6de75-d730-11db-ba1c-95447b08afa4)
=====================================
10:56:20,854 INFO [org.alfresco.repo.admin.patch.PatchExecuter]
=== Applied patch                 ===
ID: patch.webscripts3
RESULT:
Imported view into bootstrap location: / (workspace://SpacesStore/a3e6de75-d730-11db-ba1c-95447b08afa4)
=====================================
10:56:20,854 INFO [org.alfresco.repo.admin.patch.PatchExecuter]
=== Applied patch                 ===
ID: patch.webscriptsExtension
RESULT:
Imported view into bootstrap location: /app:company_home/app:dictionary (workspace://SpacesStore/a3e6de75-d730-11db-ba1c-95447b08afa4)
=====================================
10:56:20,869 INFO [org.alfresco.repo.module.ModuleServiceImpl] Found 0 module(s).