INTERNAL 4624: ROSSALColumnAccess position not found
Hi.
I have encountered this error for a specific table.
After some investigation, I found that the error occurs only when accessing one of the buddy projections.
Solution that worked:
1. Create a new super projection
2. Drop the old one
3. Rename if needed
Tagged:
0
Comments
Hi, that is the correct fix since it's usually due to a corrupt ROS index file, but we haven't seen this issue since version 7.2. Newer ROS file format and catalog improvements should not experience this issue. What version are you running?
At first the error occurred in 9.1.1-11 and again in 9.2.1-11.
Support responded that the issue fixed in 9.2.1-8 (VER-69389), but it seems that it's not the case.