Re: Attempt to write duplicate record...

Thanks to everyone that responded.

In order to account for this situation I have added an E extended to the
Write.

Thanks again,

Robert Rogerson
On 2011-11-15 1:13 PM, CRPence wrote:

On 15-Nov-2011 08:29 , Robert Rogerson wrote:

I had a stored procedure fail with RNX1021 Attempt to write a
duplicate record to file SIGNTMP.

<<SNIP>> I thought this was pretty solid code but the program still
failed. A new record is only written if a record with the same key
is not found.

Apparently not so solid ;-) at least with regard to the potential for
concurrency.


So my only explanation is that another process wrote a record with
the same key in between the Chain and the Write.

Presumably.


Am I missing something of does some have another explanation.

There are other possibilities that can arise due to nuances in how
the validation was accomplished and\or data inserted. But ssuming the
most obvious, simple, and consistent means used to lookup and then
insert the identical data as key, the most obvious origin from another
thread\process having won the race to get the insert of the previously
verified non-existent key.


<<SNIP>>

Seek the answer from the journal, comparing the timestamp the
RRN was added and that of the failed insert.

Regards, Chuck