Uploaded image for project: 'Derby'
  1. Derby
  2. DERBY-7002

Change the text of X0Y84 to advise users to tune the value of derby.language.sequence.preallocator

Attach filesAttach ScreenshotAdd voteVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Open
    • Major
    • Resolution: Unresolved
    • 10.15.1.3
    • None
    • SQL
    • None
    • Normal

    Description

      This is the LANG_TOO_MUCH_CONTENTION_ON_SEQUENCE error message. Right now it says the following:

      Too much contention on sequence {0}. This is probably caused by an uncommitted
      scan of the SYS.SYSSEQUENCES catalog. Do not query this catalog directly. 
      Instead, use the SYSCS_UTIL.SYSCS_PEEK_AT_SEQUENCE function to view
      the current value of a sequence generator.
      

      Issue DERBY-6999 suggests that it would be good if the error message suggested another cause for the "too much contention" exception: The value of derby.language.sequence.preallocator may be too low. The error message should suggest that the user tune this value.

      While we're at it, it might be good if the error message noted the current friction with Statement.getGeneratedKeys() (see DERBY-6934). Currently, there is no workaround for that friction. Application code should not call that method.

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            rhillegas Richard N. Hillegas

            Dates

              Created:
              Updated:

              Slack

                Issue deployment