Microsoft KB Archive/149932

{|
 * width="100%"|

BUG: 3307 Lock Error on INSERT SELECT UNION Abort w/ Dup Key

 * }

Q149932

-

The information in this article applies to:


 * Microsoft SQL Server version 6.0

-

BUG#: 14745 (6.00)

SYMPTOMS
An INSERT into a table with a UNIQUE CLUSTERED INDEX can fail with fatal error 3307:

Process X was expected to hold logical lock on page Y. Error while undoing log row in database 'pubs'. Rid pageid is 0xZ and row num is 0xZZ. The SQL Server is terminating this process.

CAUSE
If the insert is from UNIONed SELECT statements and there are duplicate keys (but not rows) generated such that the INSERT should fail, the 3307 error can be raised if the level of data reaches a certain threshold, somewhere around 1000 rows depending on row size.

WORKAROUND
The INSERT would otherwise fail with a non-fatal 2601 "Attempt to insert duplicate keys" error. The INDEX can be changed to use the IGNORE_DUP_KEY option so that the 2601 error is not raised.

STATUS
Microsoft has confirmed this to be a problem in Microsoft SQL Server version 6.0. This problem has been corrected in SQL Server 6.5.

Additional query words: sql60 lock index duplicate

Keywords : kbprogramming

Issue type :

Technology : kbSQLServSearch kbAudDeveloper kbSQLServ600