Document versions appear out of order after upgraded on a system running on a clustered Oracle RDBMS.
This fix allows the system to correct the order of versions 'on the fly' even though the ids of the versions in the database are not in the same order as the version labels. This normally only takes place on an multi node Oracle RDBMS as creation statements for sequence numbers did not include the ORDER clause. This also has been corrected in this fix. As this is not normally needed, an Alfresco global property must also be set for the 'on the fly' sorting to take place. This is normally specified in the tomcat/shared/classes/alfresco-global.properties file: