topic Upgrading 1.2.1 to 1.3.0 (Store does not have a root node) in Alfresco Archive

Upgrading 1.2.1 to 1.3.0 (Store does not have a root node)

rgauss — Mon, 31 Jul 2006 20:37:32 GMT

Yes, yet another upgrade problem post, hope I didn't miss an already posted solution to this.After fixing the case errors in the upgrade script (and adding those notes to the wiki) and successfully completing the MySQL changes, replacing the alfresco.war with the 1.3.0, then starting up Tomcat I get

Re: Upgrading 1.2.1 to 1.3.0 (Store does not have a root node)

derek — Tue, 01 Aug 2006 16:05:50 GMT

Hi,

14:25:21,103 ERROR [tool.hbm2ddl.SchemaUpdate] Unsuccessful: alter table child_assoc add index FKC6EFFF32A0F28D72 (child_protocol, child_identifier, child_guid), add constraint FKC6EFFF32A0F28D72 foreign key (child_protocol, child_identifier, child_guid) references node (protocol, identifier, guid)

After the upgrade using the script, the child_assoc table will look as follows:


+—————-+————–+——+—–+———+—————-+
| Field          | Type         | Null | Key | Default | Extra          |
+—————-+————–+——+—–+———+—————-+
| id             | bigint(20)   | NO   | PRI |         | auto_increment |
| parent_node_id | bigint(20)   | YES  | MUL |         |                |
| child_node_id  | bigint(20)   | YES  | MUL |         |                |
| type_qname     | varchar(255) | NO   |     |         |                |
| qname          | varchar(255) | NO   |     |         |                |
| is_primary     | bit(1)       | YES  |     |         |                |
| assoc_index    | int(11)      | YES  |     |         |                |
+—————-+————–+——+—–+———+—————-+
‍‍‍‍‍‍‍‍‍‍‍‍‍

Which WIKI page have you put the changes on?
Please check the version of the WAR file you are using, and confirm post-upgrade script execution structure of the child_assoc table.

Regards

Re: Upgrading 1.2.1 to 1.3.0 (Store does not have a root node)

rgauss — Tue, 01 Aug 2006 16:43:38 GMT

Thanks for the response.

Here's my child_assoc immediately after the SQL script:

mysql> describe child_assoc;
+—————-+————–+——+—–+———+—————-+
| Field          | Type         | Null | Key | Default | Extra          |
+—————-+————–+——+—–+———+—————-+
| id             | bigint(20)   |      | PRI | NULL    | auto_increment |
| parent_node_id | bigint(20)   | YES  | MUL | NULL    |                |
| child_node_id  | bigint(20)   | YES  | MUL | NULL    |                |
| type_qname     | varchar(255) |      |     |         |                |
| qname          | varchar(255) |      |     |         |                |
| is_primary     | tinyint(1)   | YES  |     | NULL    |                |
| assoc_index    | int(11)      | YES  |     | NULL    |                |
+—————-+————–+——+—–+———+—————-+‍‍‍‍‍‍‍‍‍‍‍‍

But after trying to startup with the new WAR I get:

mysql> describe child_assoc;
+——————-+————–+——+—–+———+—————-+
| Field             | Type         | Null | Key | Default | Extra          |
+——————-+————–+——+—–+———+—————-+
| id                | bigint(20)   |      | PRI | NULL    | auto_increment |
| parent_node_id    | bigint(20)   | YES  | MUL | NULL    |                |
| child_node_id     | bigint(20)   | YES  | MUL | NULL    |                |
| type_qname        | varchar(255) |      |     |         |                |
| qname             | varchar(255) |      |     |         |                |
| is_primary        | tinyint(1)   | YES  |     | NULL    |                |
| assoc_index       | int(11)      | YES  |     | NULL    |                |
| isPrimary         | tinyint(1)   | YES  |     | NULL    |                |
| parent_protocol   | varchar(50)  | YES  | MUL | NULL    |                |
| parent_identifier | varchar(100) | YES  |     | NULL    |                |
| parent_guid       | varchar(36)  | YES  |     | NULL    |                |
| child_protocol    | varchar(50)  | YES  | MUL | NULL    |                |
| child_identifier  | varchar(100) | YES  |     | NULL    |                |
| child_guid        | varchar(36)  | YES  |     | NULL    |                |
+——————-+————–+——+—–+———+—————-+‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

Which WIKI page have you put the changes on?

The changes I made were to this section:
http://wiki.alfresco.com/wiki/Upgrading_to_1.3.0#Installing_from_1.2.1_to_1.3.0
I just included what was relavent from upgrade.txt in the dist and the case changes.

Please check the version of the WAR file you are using

I'm using the WAR from alfresco-community-war-1.3.0.tar.gz

Thanks again.

Re: Upgrading 1.2.1 to 1.3.0 (Store does not have a root node)

trying2alfresco — Wed, 02 Aug 2006 16:10:41 GMT

I am having the same same problem. Any ideas how to solve it?

Re: Upgrading 1.2.1 to 1.3.0 (Store does not have a root node)

egabbud — Thu, 17 Aug 2006 13:10:54 GMT

Same problem here!

We did an upgrade from 1.2 (Enterprise) to 1.2.1 (Community). Everything ok.

But the 1.3 upgrade is a nightmare!

In the 1.2.1 we have, for child_assoc:

+——————-+————–+——+—–+———+——-+
| Field             | Type         | Null | Key | Default | Extra |
+——————-+————–+——+—–+———+——-+
| id                | bigint(20)   | NO   | PRI | 0       |       |
| type_qname        | varchar(255) | NO   |     | NULL    |       |
| qname             | varchar(255) | NO   |     | NULL    |       |
| isPrimary         | tinyint(1)   | YES  |     | NULL    |       |
| assoc_index       | int(11)      | YES  |     | NULL    |       |
| parent_protocol   | varchar(50)  | YES  | MUL | NULL    |       |
| parent_identifier | varchar(100) | YES  |     | NULL    |       |
| parent_guid       | varchar(36)  | YES  |     | NULL    |       |
| child_protocol    | varchar(50)  | YES  | MUL | NULL    |       |
| child_identifier  | varchar(100) | YES  |     | NULL    |       |
| child_guid        | varchar(36)  | YES  |     | NULL    |       |
+——————-+————–+——+—–+———+——-+‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

After running successfully the db upgrade script to 1.3 (with case corrected, refer to: http://forums.alfresco.com/viewtopic.php?t=2892), we have:

+—————-+————–+——+—–+———+—————-+
| Field          | Type         | Null | Key | Default | Extra          |
+—————-+————–+——+—–+———+—————-+
| id             | bigint(20)   | NO   | PRI | NULL    | auto_increment |
| parent_node_id | bigint(20)   | YES  | MUL | NULL    |                |
| child_node_id  | bigint(20)   | YES  | MUL | NULL    |                |
| type_qname     | varchar(255) | NO   |     | NULL    |                |
| qname          | varchar(255) | NO   |     | NULL    |                |
| is_primary     | bit(1)       | YES  |     | NULL    |                |
| assoc_index    | int(11)      | YES  |     | NULL    |                |
+—————-+————–+——+—–+———+—————-+‍‍‍‍‍‍‍‍‍‍‍

So obviously some columns are deleted from the table.

We then replace the alfresco.war with the one from alfresco-community-tomcat-1.3.0.tar.gz. It starts and throws:

14:31:07,810 ERROR [tool.hbm2ddl.SchemaUpdate] Unsuccessful: alter table child_assoc add index FKC6EFFF32A0F28D72 (child_protocol, child_identifier, child_guid), add constraint FKC6EFFF32A0F28D72 foreign key (child_protocol, child_identifier, child_guid) references node (protocol, identifier, guid)
14:31:07,830 ERROR [tool.hbm2ddl.SchemaUpdate] Can't create table './alfresco/#sql-3950_89.frm' (errno: 150)
14:31:07,843 ERROR [tool.hbm2ddl.SchemaUpdate] Unsuccessful: alter table child_assoc add index FKC6EFFF3294135688 (parent_protocol,
parent_identifier, parent_guid), add constraint FKC6EFFF3294135688 foreign key (parent_protocol, parent_identifier, parent_guid) references node (protocol, identifier, guid)
14:31:07,843 ERROR [tool.hbm2ddl.SchemaUpdate] Can't create table './alfresco/#sql-3950_89.frm' (errno: 150)‍‍‍‍‍

followed by

14:31:25,594 ERROR [web.context.ContextLoader] Context initialization failed
org.alfresco.service.cmr.repository.InvalidStoreRefException: Store does not have a root node
        at org.alfresco.repo.node.db.DbNodeServiceImpl.getRootNode(DbNodeServiceImpl.java:206)
‍‍‍‍

and many other errors.

The question is:
Why is it trying to alter child_assoc and add an index on UNEXISTING FIELDS at this moment??

As hibernate.hbm2ddl.auto=update is set in classes/alfresco/domain/hibernate-cfg.properties, the tables are then updated, to the following:

+——————-+————–+——+—–+———+—————-+
| Field             | Type         | Null | Key | Default | Extra          |
+——————-+————–+——+—–+———+—————-+
| id                | bigint(20)   | NO   | PRI | NULL    | auto_increment |
| parent_node_id    | bigint(20)   | YES  | MUL | NULL    |                |
| child_node_id     | bigint(20)   | YES  | MUL | NULL    |                |
| type_qname        | varchar(255) | NO   |     | NULL    |                |
| qname             | varchar(255) | NO   |     | NULL    |                |
| is_primary        | bit(1)       | YES  |     | NULL    |                |
| assoc_index       | int(11)      | YES  |     | NULL    |                |
| isPrimary         | bit(1)       | YES  |     | NULL    |                |
| parent_protocol   | varchar(50)  | YES  |     | NULL    |                |
| parent_identifier | varchar(100) | YES  |     | NULL    |                |
| parent_guid       | varchar(36)  | YES  |     | NULL    |                |
| child_protocol    | varchar(50)  | YES  |     | NULL    |                |
| child_identifier  | varchar(100) | YES  |     | NULL    |                |
| child_guid        | varchar(36)  | YES  |     | NULL    |                |
+——————-+————–+——+—–+———+—————-+‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

I guess there are errors in Node.hbm.xml or somewhere around this point… Have you identied the issues yet?
Why do we now have is_primary and isPrimary fields???
How can we eventualy update to the 1.3?

Thanks,
Emmanuel

Re: Upgrading 1.2.1 to 1.3.0 (Store does not have a root node)

derek — Thu, 17 Aug 2006 15:22:56 GMT

Hi,

They're the scripts for the 1.3 line, which is currently at 1.3.1. If you have the enterprise release of 1.3.1, then it'll work. If you are using the Open Source version, then you'll need the latest code off HEAD in order to be compatible with the scripts.

Otherwise you are running scripts that are designed for later code. The war node.hbm.xml is too old for the scripts. Build a war from HEAD and then do the upgrade again and you should be fine.

Regards

Re: Upgrading 1.2.1 to 1.3.0 (Store does not have a root node)

egabbud — Mon, 21 Aug 2006 14:32:12 GMT

Derek, thanks for your help!
But I still get exactly the same errors…

I checked the latest version from SVN.
- HEAD/root/projects/installer/upgrade/scripts/AlfrescoSchemaMigrate-1.3-mysql.sql is still containing case errors (which I corrected manually). DB migration is fine.
- HEAD/root/projects/repository/source/java/org/alfresco/repo/domain/hibernate/Node.hbm.xml has not changed since many revisions, in countrary of what I understood from your latest post.

So clearly, upgrading from 1.2.1 to 1.3 latest code off HEAD still doesn't work! Quite weird…