[DERBY-5494] Same value returned by successive calls to a sequence generator flanking an unorderly shutdown.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.6.1.0, 10.6.2.1, 10.7.1.1, 10.8.1.2, 10.8.2.2, 10.9.1.0
• Fix Version/s: 10.9.1.0, 10.10.1.1
• Component/s: SQL
• Labels: derby_backport_reject_10_8 derby_triage10_9
• Urgency: Normal
• Issue & fix info: High Value Fix, Known fix, Patch Available, Repro attached
• Bug behavior facts: Deviation from standard
• Assignee: Mike Matrigali
• Reporter: Richard N. Hillegas
• Created: 07/Nov/11 14:07
• Updated: 14/Jun/13 17:19
• Resolved: 31/May/12 18:47

Description

The following sequence of steps causes a sequence generator to return the same value on successive NEXT VALUE FOR calls.

1) Bring up ij and issue the following commands:

connect 'jdbc:derby:db;create=true';

create sequence s;
values next value for s;

2) Control-c out of ij so that the engine comes down hard without an orderly shutdown.

3) Now bring up ij again and issue the following commands:

connect 'jdbc:derby:db';

values next value for s;

Thanks to Knut for finding this one.

Issue Links

• breaks: DERBY-5780 identity column performance has degredated
• is related to: DERBY-5495 Master issue to track fixes to sequence generators
• is related to: DERBY-5697 Doc changes to account for correctness fixes for sequences
• is related to: DERBY-5443 reduce number of times sequence updater does it work on user thread rather than nested user thread.