-
Type:
Service Pack Request
-
Status: Closed
-
Resolution: Fixed
-
Affects Version/s: 4.1.4
-
Fix Version/s: 4.1.6
-
Component/s: Repository, Upgrades
-
Labels:None
-
Bug Priority:
-
ACT Numbers:
69540
-
Build Location:
If an Oracle sequence is created without clause “ORDERED” it can can have undesirable side effects when using ORCLE RAC.
How to reproduce ?:
Install a 3.2 out of te box on Oracle RAC.
Create a rule adding versionable aspect to all documents.
Create some documents with some versions
Upgrade to 4.1.4
Create additional versions util getting an error
Observed result :
You should get the error like « Unexpected: current version does not appear to be 1st version in the list
[workspace://version2Store/d3f21c3c-af96-40b8-8c15-070a89a8a084, workspace://SpacesStore/a7540095-e9e5-42e2-a0e2-231014f09967] »
Expected result :
No error.
Notes/Hints :
- If an out of the box 4.1.4 version is installed on RAC and if it is not the result of an upgrade then it works fine because sequences are all created in “AlfrescoCreate-RepoTables.sql” with the ORDER clause.
- If sequences are created during an upgrade from a version before 3.2.x then sequences are created without the “ORDER” clause in upgrade/3.3/org.alfresco.repo.domain.hibernate.dialect.AlfrescoOracle9Dialect/fix-repo-seqs.sql