Xavier Maillard wrote:
May be due to CR 277087, fixed in 188.8.131.52 |
"A 1530 error, "Create index with sorted_data was aborted
because of row out of order. Primary key of first out of
order row is '<value>'", may occassionally be reported
when an ALTER TABLE MODIFY command is executed on a
data-only locked table and the table has a clustered
As a quick workaround/alternative to applying the current
rollup, you could try dropping
the clustered index, then add the column, then recreate
Can this occur also on a ASE 184.108.40.206 release ?
I think so. The fix was also provided in 220.127.116.11 IR.