Identity column and 40XL1 error

26 messages Options
Identity column and 40XL1 error – Hello, I am facing 40XL1 error when I try to insert rows into a table with an identity column. Identity column has been created using "id...
On 18/05/2017 08:29, Abhirama wrote: > Hello, > > I am facing 40XL1 error when I try to insert rows into a table with an > identit...
As you can see from my post, lock is denied because of "values identity_val_local()" issued by a competing insert on the same table. Th...
On 18/05/2017 12:20, Abhirama wrote: > As you can see from my post, lock is denied because of "values > identity_val_local()" is...
Hi Abhi, You may have tripped across a problem with the IDENTITY_VAL_LOCAL() function. When identity columns were re-worked to use sequence ...
Rick, My code is not explicitly firing IDENTITY_VAL_LOCAL() call, my best guess is hibernate, but I can confirm this by enabling hibernate log...
On 5/18/17 9:12 PM, Abhirama wrote: > Rick, > > My code is not explicitly firing IDENTITY_VAL_LOCAL() call, my best > guess is hi...
Hello Rick, With your guidance I was able to dig more into the problem. IDENTITY_VAL_LOCAL() is not being issued by hibernate but by Derby i...
Hi Abhi, Thanks for investigating further. You have uncovered a defect in Derby's implementation of Statement.getGeneratedKeys(). The defect ...
Hi Abhi, Here is one more idea. I believe that you said that you are running an in-memory database. That means that you do not need to worry ...
Rick, Thanks for your help in debugging the problem. I run in memory only while testing, actual application does use persistent file system...
Rick Hillegas-3 wrote > Hi Abhi, > > Here is one more idea. I believe that you said that you are running an > in-memory database...
Can you share the derby.log for this problem? Thanks, -Rick On 3/29/18 1:45 AM, palo.liska wrote: > Rick Hillegas-3 wrote >> Hi ...
Sorry, I realized the property was not set. Now I got something else )) Derby could not obtain the locks needed to release the unused, prealloc...
Rick Hillegas-3 wrote > Can you share the derby.log for this problem? Finally, I have derby.log, even with derby.language.sequence.preall...
Thanks for attaching derby.log. A couple things jump out at me: 1) Something about the problem description is not clear. The first tooMuchCon...
Rick Hillegas-3 wrote > 1) Something about the problem description is not clear. The first > tooMuchContention exception occurs within a ...
On 4/6/18 6:07 AM, palo.liska wrote: > Rick Hillegas-3 wrote >> 1) Something about the problem description is not clear. The first >...
Rick Hillegas-3 wrote > Technically, Hibernate should not be calling getGeneratedKeys() because > Derby's DatabaseMetaData says that the ...
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...
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 ...
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 >...
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...
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 &g...
Hi, bug created: https://issues.apache.org/jira/browse/DERBY-6999 Palo. -- Sent from: http://apache-database.10148.n7.nabble.com/Apac...
On 6/20/18 2:40 AM, palo.liska wrote: > Hi, > bug created: https://issues.apache.org/jira/browse/DERBY-6999 > > Palo. > > ...