upgrade 2.1 -> 3.0

ra74 — Wed, 26 Aug 2009 13:13:24 GMT

HelloI've decided to upgrade our alfresco 2.1 installation to 3.0 due to I hope fixed a few severe bugs and because new version store implemenation. Our database has grown so fast that we've problem to manage itBecause Oracle database is not supported in community edition I've ported mysql scripts-

Re: upgrade 2.1 -> 3.0

ra74 — Wed, 02 Sep 2009 13:17:35 GMT

So what I've found.
The problem comes from method HibernateNodeDaoServiceImpl.getChildAssoc(final Long parentNodeId, final QName assocTypeQName, final String childName)

The following query is executed to find "org" child, parent is "Web Scripts"


select
         assoc
      from
         org.alfresco.repo.domain.hibernate.ChildAssocImpl as assoc
      where
         assoc.parent.id = :parentId and
         assoc.typeQNameId = :typeQNameId and
         assoc.childNodeNameCrc = :childNodeNameCrc and
         assoc.childNodeName = :childNodeName
      order by
         assoc.index,
         assoc.id
‍‍‍‍‍‍‍‍‍‍‍‍‍‍

But values in the database in the table alf_child_assoc for the "org" child are:
child_node_name_crc = -1
child_node_name is an uuid
qname_localname is org so it's correct

I see there's a patch FixNameCrcValuesPatch but it touches rows where qname localname is "name". Afterwards childNodeName is wrong

Everything seems clear - there is no patch to fix child_node_name. But it's working on mysql and I've performed upgrade at my home without any problems on the oracle express

Edit: At home I've fresh alfresco 2.1 installation: child_node_name is just the node name i.e. org, at work child_node_name value is an uuid string but as I remeber it's not real (frozen) uuid of this node
Any idea why it's happen ?

Edit 2: I've the found the reason. There're some customization in our alfresco and in the file contentModel.xml property 'duplicate' for the type cm:folder has been changed to 'true'

topic Re: upgrade 2.1 -> 3.0 in Alfresco Archive

upgrade 2.1 -> 3.0

Re: upgrade 2.1 -> 3.0