 | |
#1
 
| |||
| |||
|
Re: Urgent Help needed -
07-03-2008
, 05:20 AM
|
May be due to CR 277087, fixed in 12.5.0.2 "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 index." As a quick workaround/alternative to applying the current rollup, you could try dropping the clustered index, then add the column, then recreate the index. |
Regards
#2
| |||
| |||
|
|
May be due to CR 277087, fixed in 12.5.0.2 "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 index." As a quick workaround/alternative to applying the current rollup, you could try dropping the clustered index, then add the column, then recreate the index. |
Regards
#3
| |||
| |||
|
|
May be due to CR 277087, fixed in 12.5.0.2 "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 index." As a quick workaround/alternative to applying the current rollup, you could try dropping the clustered index, then add the column, then recreate the index. |
Regards
#4
| |||
| |||
|
|
May be due to CR 277087, fixed in 12.5.0.2 "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 index." As a quick workaround/alternative to applying the current rollup, you could try dropping the clustered index, then add the column, then recreate the index. |
Regards
#5
| |||
| |||
|
|
May be due to CR 277087, fixed in 12.5.0.2 "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 index." As a quick workaround/alternative to applying the current rollup, you could try dropping the clustered index, then add the column, then recreate the index. |
Regards
#6
| |||
| |||
|
|
May be due to CR 277087, fixed in 12.5.0.2 "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 index." As a quick workaround/alternative to applying the current rollup, you could try dropping the clustered index, then add the column, then recreate the index. |
Regards
#7
| |||
| |||
|
|
May be due to CR 277087, fixed in 12.5.0.2 "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 index." As a quick workaround/alternative to applying the current rollup, you could try dropping the clustered index, then add the column, then recreate the index. |
Regards
#8
| |||
| |||
|
|
May be due to CR 277087, fixed in 12.5.0.2 "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 index." As a quick workaround/alternative to applying the current rollup, you could try dropping the clustered index, then add the column, then recreate the index. |
Regards
#9
| |||
| |||
|
|
May be due to CR 277087, fixed in 12.5.0.2 "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 index." As a quick workaround/alternative to applying the current rollup, you could try dropping the clustered index, then add the column, then recreate the index. |
Regards
#10
| |||
| |||
|
|
May be due to CR 277087, fixed in 12.5.0.2 "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 index." As a quick workaround/alternative to applying the current rollup, you could try dropping the clustered index, then add the column, then recreate the index. |
Regards
 |
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2013, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2013, Jelsoft Enterprises Ltd.