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

jey
Champ in-the-making
Champ in-the-making
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.

lateral
Champ in-the-making
Champ in-the-making
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

paulhh
Champ in-the-making
Champ in-the-making
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.

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

lateral
Champ in-the-making
Champ in-the-making
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?

derek
Star Contributor
Star Contributor
Post the log, please.

lateral
Champ in-the-making
Champ in-the-making
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

lateral
Champ in-the-making
Champ in-the-making
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?

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

lateral
Champ in-the-making
Champ in-the-making
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).