Re: sql identity column generate always (WHY HAVE TO RESET)

[Sam_L <lennon_s_j@xxxxxxxxxxx>]

Late to this discussion, but here's my two cents:

Me, I'd like to figure out which program/process wrote the original 
record that is now being duplicated.

Journaling the file should pin that down.

If both the original process and the one writing the duplicate value 
seem to be coded correctly, then it looks like you have a good case for 
convincing IBM that there is a bug in the database manager.

And presumably you are up to date on the OS and PTFs.

Sam

On 5/24/2019 9:26 AM, Jay Vaughn wrote:
> id BIGINT NOT NULL GENERATED  ALWAYS AS IDENTITY
>     (START WITH 1 INCREMENT BY 1)
> primary key(id)
>
> We all know that sometimes the identity column gets "out of whack" and that
> we have to reset it with the alter/restart...
>
> My question is why does it get out of whack.
> Even better question, how can we detect the presence of the out of
> whackness before we are faced with a "attempt to write duplicate" because
> it was "out of whack"?
> Is there a system table we can query to look at to detect these time bombs?
>
> Abused google looking for an answer and everyone prides themselves with how
> to restart it... and never is it explained how to detect them beforehand.
>
> TIA
>
> jay