Integrity Error after Alfresco Upgrade

[texano]

Hi,

I've upgrade my Alfresco installation with 20GB repository content from 4.2.C to the newest 5.0.D.
Now we are having errors related to "Mandatory property not set" and "node.integrity.IntegrityException" when creating new sites, viewing tasks, etc. This errors are show in Alfresco Share page and in catalina.out logs.
Please check the attached files.


2015-04-25 19:57:54,094  ERROR [extensions.webscripts.AbstractRuntime] [http-apr-8080-exec-8] Exception from executeScript - redirecting to status template error: 03250167 Found 1 integrity violations:
Mandatory property not set:
   Node: workspace://SpacesStore/32fddf43-103a-4f48-b001-b48552dff3ad
   Name: 32fddf43-103a-4f48-b001-b48552dff3ad
   Type: {http://www.alfresco.org/model/content/1.0}person
   Property: {http://www.alfresco.org/model/content/1.0}sizeCurrent
org.alfresco.repo.node.integrity.IntegrityException: 03250167 Found 1 integrity violations:
Mandatory property not set:
   Node: workspace://SpacesStore/32fddf43-103a-4f48-b001-b48552dff3ad
   Name: 32fddf43-103a-4f48-b001-b48552dff3ad
   Type: {http://www.alfresco.org/model/content/1.0}person
   Property: {http://www.alfresco.org/model/content/1.0}sizeCurrent
        at org.alfresco.repo.node.integrity.IntegrityChecker.checkIntegrity(IntegrityChecker.java:664)
        at org.alfresco.repo.node.integrity.IntegrityChecker.beforeCommit(IntegrityChecker.java:766)




Can you guys help me with this?

Thank you.

[s_palyukh]

I believe 102020's solution should work, but we have fixed this issue by executing the following script:

var all = people.getPeople("");
​
for (var i=0 ; i < all.length; i++){
   
   var user = search.findNode(all);
​
   if(user.properties.sizeCurrent === null){
      
      user.properties.sizeCurrent = 0;
         
      user.save();
​
   }
}
‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

[tuscany22]

Hi there- struggled with this after I did a server to server upgrade from 4.0-e to 5.0-d. Had convinced myself I had an indexing issue also and spent quite a bit of time on it. Setting quotas to "on" and updating the db did solve the error I was getting. Thanks 102020 . Wish this has been posted a month ago.

[jforeman]

@102020 This worked! Much appreciated.

[koopa]

Worked for me too @102020. Why do you suggest to disable schema update? And when should I disable it?