One thing I’d like to highlight is that SequenceInformation insists on long for max and min values. Since Oracle sequences can easily exceed those limits, I wonder if this needs to be discussed further. More over the conversion BigDecimal.longValue() looses precision and also might result in a value with the opposite sign.