Unable to create or alter sequence "XXX" because of invalid attributes (start value "1", min value "1", max value "9223372036854775807", increment "1"); SQL statement: alter sequence deployment_items_table_seq RESTART WITH (select max (id) from deployment_items_table ) + 1; [90009-176]

[GoogleCodeExporter]

Please send a question to the H2 Google Group or StackOverflow first,
and only then, once you are completely sure it is an issue, submit it here.
The reason is that only very few people actively monitor the issue tracker.

Before submitting a bug, please also check the FAQ:
http://www.h2database.com/html/faq.html

What steps will reproduce the problem?
(simple SQL scripts or simple standalone applications are preferred)
  Please see issue 547; it was closed, but I'm still seeing it.

What is the expected output? What do you see instead?

What version of the product are you using?
1.3.176

 On what operating system, file
system, and virtual machine?
Windows 8 and Linux

Do you know a workaround?
Yes, drop back to 1.3.173

What is your use case, meaning why do you need this feature?
I just need continuity in the product; I have a few customers with legacy DBs, 
and I can't update their versions.

How important/urgent is the problem for you?
Very important; it's preventing me from upgrading to 1.3.176.

Please provide any additional information below.

Original issue reported on code.google.com by odranoe...@gmail.com on 17 Sep 2014 at 9:45

[GoogleCodeExporter]

I see in the code that the error message is wrong (it contains the wrong 
values). I will fix that.

But please understand you need to provide a complete, reproducible test case. 
Obviously, I don't know what "max (id) from deployment_items_table" is, and I 
don't know how you defined your sequence.

Original comment by thomas.t...@gmail.com on 17 Sep 2014 at 8:42

• Changed state: Invalid

[GoogleCodeExporter]

Hi,

  I had attached the whole DB in the original issue.  Please look at issue 547

Original comment by odranoe...@gmail.com on 17 Sep 2014 at 8:49

[GoogleCodeExporter]

Hi,

  I attached the whole DB in the original issue.

Original comment by odranoe...@gmail.com on 17 Sep 2014 at 8:50

[GoogleCodeExporter]

OK I see. I will have a look at it.

Original comment by thomas.t...@gmail.com on 18 Sep 2014 at 4:52

• Changed state: New

[GoogleCodeExporter]

You can use version 1.4.184 and add the option "MV_STORE=false" to your DB URL 
to get this fix

Original comment by noelgrandin on 6 Jan 2015 at 7:52

• Changed state: Fixed