Upgrade from 3b to 3c

[hreintke]

LS,

I have working Labs 3b installation with default configuration settings on databases and locations. So my idea is that all info is stored in the alf_data directory.
In the (generic) upgrade documentation is mentioned :
- copy the content
- Use db backup & restore for the DB content
As the DB used is Derby  (according to the Derby website) an offline backup and restore is done by copying the files.

So what I did was installing 3c in a new directory, copied the alf_data directory to the new location and started 3c.

But the I get the following error

11:35:40,671  INFO  [domain.schema.SchemaBootstrap] Alfresco is using the Apache Derby default database. Please only use this while evaluating Alfresco, it is NOT recommended for production or deployment!
11:35:41,687  ERROR [domain.schema.SchemaBootstrap] Schema auto-update failed org.alfresco.error.AlfrescoRuntimeException: The schema script could not be found at location classpath:alfresco/dbscripts/upgrade/2.2/${db.script.dialect}/upgrade-from-2.2SP1.sql

Question :

Do I need to specify/configure other settings or run upgrade scripts to be able to upgrade my system to 3c ?

Kind regards,

Herman

[joglekar]

I am also getting exactly same message and Error.
Result Alfresco not starting

It looks like at  start up auto upgrade scripts are detecting previous installation as 2.2 instead of 3.0b.

I am using Alfresco on fedora-9 and postgresql 8.3.1 version 3b is working.

INFO  [service.descriptor.DescriptorService] Alfresco started (Labs): Current version 3.0.0 (b 1164) schema 131 - Installed version 3.0.0 (b 1164) schema 131

thanks and regards

Joglekar

[niklas_sjostrom]

I also upgraded from 3b to 3c with what seems to be a little bit strange result.

I started with a working MySQL Alfresco Labs 3b installation and did a new install of 3c and then inserted the ./alf_data directory and kept the database.

At the first start-up after the upgrade it seems to run org.alfresco.repo.domain.schema.SchemaBootstrap- and org.alfresco.repo.admin.patch.PatchExecuter-commands whose names seem to reference 2.1- and 2.2-versions. Should these be run even though the original installation was a 3b?

The reason I'm asking is because even though all commands seem to run without error the end-result is a notice about a schema version mismatch between current version and the installed one.

Alfresco started (Labs): Current version 3.0.0 (c 1342) schema 1000 - Installed version 3.0.0 (b 1164) schema 131

Should I worry about this?

In my case Alfresco starts and seems to be running ok. The schema version mismatch has me a bit worried however.

Best Regards!
–nicke


(Relevant log entries from first start-up included below.)

(stuff deleted…)

09:12:15,491 INFO  [org.alfresco.repo.domain.schema.SchemaBootstrap] Schema managed by database dialect org.hibernate.dialect.MySQLInnoDBDialect.
09:12:15,764 INFO  [org.alfresco.repo.domain.schema.SchemaBootstrap] Executing database script /opt/Alfresco/tomcat/temp/Alfresco/AlfrescoSchemaUpdate-org.hibernate.dialect.MySQLInnoDBDialect-25111.sql (Copied from classpath:alfresco/dbscripts/upgrade/2.2/org.hibernate.dialect.MySQLInnoDBDialect/upgrade-from-2.2SP1.sql).
09:12:18,719 INFO  [org.alfresco.repo.domain.schema.SchemaBootstrap] Executing database script /opt/Alfresco/tomcat/temp/Alfresco/AlfrescoSchemaUpdate-org.hibernate.dialect.MySQLInnoDBDialect-25112.sql (Copied from classpath:alfresco/dbscripts/upgrade/2.2/org.hibernate.dialect.MySQLInnoDBDialect/AlfrescoSchemaUpdate-Person.sql).
09:12:18,746 INFO  [org.alfresco.repo.domain.schema.SchemaBootstrap] Executing database script /opt/Alfresco/tomcat/temp/Alfresco/AlfrescoSchemaUpdate-org.hibernate.dialect.MySQLInnoDBDialect-25113.sql (Copied from classpath:alfresco/dbscripts/upgrade/2.2/org.hibernate.dialect.MySQLInnoDBDialect/AlfrescoSchemaUpdate-OrclBLOB.sql).
09:12:20,092 INFO  [org.alfresco.repo.domain.schema.SchemaBootstrap] Executing database script /opt/Alfresco/tomcat/temp/Alfresco/AlfrescoSchemaUpdate-org.hibernate.dialect.MySQLInnoDBDialect-25114.sql (Copied from classpath:alfresco/dbscripts/upgrade/2.2/org.hibernate.dialect.MySQLInnoDBDialect/AlfrescoSchemaUpdate-2.1-AuditPathIndex.sql).
09:12:20,196 INFO  [org.alfresco.repo.domain.schema.SchemaBootstrap] All executed statements written to file /opt/Alfresco/tomcat/temp/Alfresco/AlfrescoSchemaUpdate-All_Statements-25115.sql.

(stuff deleted…)

09:12:22,101 WARN  [org.alfresco.repo.node.index.FullIndexRecoveryComponent] The indexes are not synchronized with the database.
09:12:22,685 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:12:22,685 INFO  [org.alfresco.repo.admin.ConfigurationChecker] The Alfresco root data directory ('dir.root') is: ./alf_data
09:12:22,746 INFO  [org.alfresco.repo.admin.patch.PatchExecuter] Checking for patches to apply …
09:12:23,033 INFO  [org.alfresco.repo.admin.patch.PatchExecuter]        Applying patch 'patch.calendarNamespaceUri' (Update the Calendar model namespace URI and reindex all calendar objects.).
09:12:23,148 INFO  [org.alfresco.repo.admin.patch.PatchExecuter]        Applying patch 'patch.spacesStoreGuestPermission' (Sets READ permissions for GUEST on root node of the SpacesStore.).
09:12:24,167 INFO  [org.alfresco.repo.admin.patch.PatchExecuter]
=== Applied patch                 ===
ID: patch.calendarNamespaceUri
RESULT:
Updated the Calendar model namespace URI to http://www.alfresco.org/model/calendar and reindexed 0 calendar objects.
=====================================
09:12:24,167 INFO  [org.alfresco.repo.admin.patch.PatchExecuter]
=== Applied patch                 ===
ID: patch.db-V2.1-AuditPathIndex
RESULT:
Script completed
=====================================
09:12:24,168 INFO  [org.alfresco.repo.admin.patch.PatchExecuter]
=== Applied patch                 ===
ID: patch.db-V2.2-OrclBLOB
RESULT:
Script completed
=====================================
09:12:24,168 INFO  [org.alfresco.repo.admin.patch.PatchExecuter]
=== Applied patch                 ===
ID: patch.db-V2.2-Person
RESULT:
Script completed
=====================================
09:12:24,168 INFO  [org.alfresco.repo.admin.patch.PatchExecuter]
=== Applied patch                 ===
ID: patch.db-V2.2-Upgrade-From-2.2SP1
RESULT:
Script completed
=====================================
09:12:24,168 INFO  [org.alfresco.repo.admin.patch.PatchExecuter]
=== Applied patch                 ===
ID: patch.spacesStoreGuestPermission
RESULT:
Granted READ permissions for GUEST on root node of the SpacesStore.
=====================================

(stuff deleted…)

09:12:29,672 INFO  [org.alfresco.service.descriptor.DescriptorService] Alfresco started (Labs): Current version 3.0.0 (c 1342) schema 1000 - Installed version 3.0.0 (b 1164) schema 131

‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

[mikeh]

It's not a mismatch - it just informational and indicates that you've upgraded since the first database bootstrap.

Mike

[niklas_sjostrom]

It's not a mismatch - it just informational and indicates that you've upgraded since the first database bootstrap.

Mike

Ok, great! Chalk up another successful 3b -> 3c upgrade then.

Thank you for clarifying that Mike.

–nicke

[hreintke]

LS,

Since I am running the default Derby database. Which upgrade scripts are supposed to be run ?

Looking in the dbscripts/upgrade directory I have directories for 1.3, 1.4, 2.0, 2.1 and 2.2.

From the earlier posts I expect that the 2.2 scripts are the right one ??
In the 2.2 directory I have
org.hibernate.dialect.Dialect
org.hibernate.dialect.MysqlInnodbdialect
org.hibernate.dialect.Oracle9Dialect

Questions:

Are the scripts in  ..Dialect the ones for the Derby DB ?
How does Alfresco select the scripts to run ?
Can I run the scripts manually to upgrade ?

Kind regards,

Herman