Rick Hillegas-3 wrote
> 1) Something about the problem description is not clear. The first
> tooMuchContention exception occurs within a half minute of booting the
> database. It is very hard to understand how your application could chew
> through 2 billion sequence numbers in that short time pe
Rick Hillegas-3 wrote
> I'm afraid I cannot make sense of the attached stack trace. There is no
> reason that a SequenceUpdater would be called while executing a "select
> count(*) ..." query. It is hard to believe that that is the stack trace
> corresponding to a deadlock on "select count(*) ..
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
tooMuchContention exception occurs within a half minute of booting the
database. It is very hard to understand how your application could chew
through 2 billion sequence
