We went live with SQL2012 SP1 and have run into a problem with duplicate keys on a clustered index for a table that has an IDENTITY column. This is code that has been working for atleast 5 years.
When the jobs was rerun, the new unique key was generated and the problem went away.
Has anybody come across this in SQL2012 SP1 ?
Starting bp_updt_clm_wrk_stat_rlse Jan 2 2013 8:30PM [SQLSTATE 01000]
Msg 2601, Sev 14, State 1, Line 288 : Cannot insert duplicate key row in object 'dbo.CLM_WORK_RELEASE_STAT' with unique index 'xcwrkrlsstat01'. The duplicate key value is (1018315). [SQLSTATE 23000]
Msg 3621, Sev 14, State 1, Line 288 : The statement has been terminated. [SQLSTATE 01000]
SQL Insert of new work release rows failed. [SQLSTATE 01000]
Begin Send Message Jan 2 2013 8:30PM [SQLSTATE 01000]
Job 'bj_email_page' started successfully. [SQLSTATE 01000]
starting bp_wait_on_job Jan 2 2013 8:30PM [SQLSTATE 01000]
0 [SQLSTATE 01000]
msg = bp_updt_clm_wrk_stat_rlse failed at Jan 2 2013 8:30PM / bp_updt_clm_wrk_stat_rlse failed with a return code -230 [SQLSTATE 01000]
End Send Message [SQLSTATE 01000]
Ending bp_updt_clm_wrk_stat_rlse Jan 2 2013 8:31PM [SQLSTATE 01000]
Begin Send Message Jan 2 2013 8:31PM [SQLSTATE 01000]
Job 'bj_email_page' started successfully. [SQLSTATE 01000]
starting bp_wait_on_job Jan 2 2013 8:31PM [SQLSTATE 01000]
0 [SQLSTATE 01000]
msg = bp_updt_clm_dims failed at Jan 2 2013 8:31PM / bp_updt_clm_dims failed with a return code -230 [SQLSTATE 01000]
End Send Message [SQLSTATE 01000]
Ending bp_updt_clm_dims Jan 2 2013 8:32PM [SQLSTATE 01000]
Msg 50000, Sev 11, State 1, Line 4 : job aborted with return code = -230 [SQLSTATE 42000]
ramesh bala