AnsweredAssumed Answered

Error patch.thumbnailsAssocQName from 3.1.0 to 4.0.1

Question asked by jigen74 on Sep 25, 2012
Hi all,
we are migrating our alfresco 3.1.0 enterprise to 4.0.1 enterprise.
We don't use base alfresco, we have a custom explorer interface.
Starting from a 3.1.0 db dump + alf_data, we deploy our app on alfresco 4.0.1.
The upgrade process breaks while applying the patch 'patch.thumbnailsAssocQName', with error:

- alfresco.log
12:44:44,440 INFO [org.alfresco.repo.admin.patch.PatchExecuter] Checking for patches to apply …
12:44:45,173 INFO [org.alfresco.repo.admin.patch.PatchExecuter] Applying patch 'patch.thumbnailsAssocQName' (Update the 'cm:thumbnails' association QName to 'rn:rendition'.).
12:44:45,256 ERROR [org.alfresco.repo.admin.patch.PatchExecuter] 08250001 java.lang.NullPointerException

12:45:23,005 ERROR [org.springframework.web.context.ContextLoader] Context initialization failed
org.alfresco.error.AlfrescoRuntimeException: 08250002 Not all patches could be applied
- catalina.out
### Error updating database. Cause: java.sql.SQLException: ORA-01461: si può eseguire associazione di valore LONG solo per inserirlo in una colonna LONG

### The error may involve alfresco.appliedpatch.update_AppliedPatch-Inline
### The error occurred while setting parameters
### Cause: java.sql.SQLException: ORA-01461: si può eseguire associazione di valore LONG solo per inserirlo in una colonna LONG

; uncategorized SQLException for SQL []; SQL state [72000]; error code [1461]; ORA-01461: si può eseguire associazione di valore LONG solo per inserirlo in una colonna LONG
; nested exception is java.sql.SQLException: ORA-01461: si può eseguire associazione di valore LONG solo per inserirlo in una colonna LONG

Commenting that patch in patch-services-context.xml, the upgrade process seems to finish ok.

We are using:
- Alfresco: 4.0.1 enterprise
- Oracle: 11.1.0.7
- Tomcat: 6.0.28
- Java: 1.6.0_10 (64bit)
on a server Linux with SUSE Linux Enterprise Server 10 SP2 (x86_64).

We tested also with Oracle 10 XE on an Ubuntu server 32bit and we got the same error.

How can we fix that error?

Regards,
Alberto

Outcomes