You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-user@db.apache.org by "palo.liska" <pa...@gmail.com> on 2018/06/08 13:59:44 UTC
Re: Identity column and 40XL1 error
Rick Hillegas-3 wrote
> On 4/10/18 4:19 AM, palo.liska wrote:
>> Rick Hillegas-3 wrote
>>> Can you make this error occur in a new database, one which hasn't
>>> already exhausted the ranges of its identity columns and sequence
>>> generators? If you can, then I recommend the following next steps:
> I was able to reproduce this issue with many concurrent inserts.
> The setup is set of threads inserting random entries in loop, and another
> set of threads concurrently updating last entry in table (actually done by
> count = select count(*) and then update .. where id=count-1).
> With this setup I have high chance of 40XL1 error.
> If requested I will share actual code.
--
Sent from: http://apache-database.10148.n7.nabble.com/Apache-Derby-Users-f95095.html
Re: Identity column and 40XL1 error
Posted by Rick Hillegas <ri...@gmail.com>.
On 6/20/18 2:40 AM, palo.liska wrote:
> Hi,
> bug created: https://issues.apache.org/jira/browse/DERBY-6999
>
> Palo.
>
>
>
> --
> Sent from: http://apache-database.10148.n7.nabble.com/Apache-Derby-Users-f95095.html
>
Thanks, Palo. Let's continue the discussion on DERBY-6999.
Re: Identity column and 40XL1 error
Posted by "palo.liska" <pa...@gmail.com>.
Hi,
bug created: https://issues.apache.org/jira/browse/DERBY-6999
Palo.
--
Sent from: http://apache-database.10148.n7.nabble.com/Apache-Derby-Users-f95095.html
Re: Identity column and 40XL1 error
Posted by Rick Hillegas <ri...@gmail.com>.
Great. Can you log a bug and attach the code to the bug?
Thanks,
-Rick
On 6/8/18 6:59 AM, palo.liska wrote:
> Rick Hillegas-3 wrote
>> On 4/10/18 4:19 AM, palo.liska wrote:
>>> Rick Hillegas-3 wrote
>>>> Can you make this error occur in a new database, one which hasn't
>>>> already exhausted the ranges of its identity columns and sequence
>>>> generators? If you can, then I recommend the following next steps:
>> I was able to reproduce this issue with many concurrent inserts.
>> The setup is set of threads inserting random entries in loop, and another
>> set of threads concurrently updating last entry in table (actually done by
>> count = select count(*) and then update .. where id=count-1).
>> With this setup I have high chance of 40XL1 error.
>> If requested I will share actual code.
>
>
>
>
> --
> Sent from: http://apache-database.10148.n7.nabble.com/Apache-Derby-Users-f95095.html
>