× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. May 2019

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

I'd try the RFE site. It's running REALLY slow today though. Existing RFE's on this are related but not exactly what you are looking for.
I suspect you're looking for something like
select
system_table_schema,
system_table_name,
system_column_name,
is_identity,
identity_maximum,
'mythical_identity_next' as mythical_identity_next
from qsys2.syscolumns a
where system_table_name = 'DELETETHIS'
and system_table_schema = 'ROB'
and is_identity='YES'
;
Then you could join that out to select max(myidcol) from ...
And find your issue?
Or list those where mythical_identity_next is approaching identity_maximum?
I searched the file API's and none of them seemed to return that either.


-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Jay Vaughn
Sent: Friday, May 24, 2019 10:23 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: sql identity column generate always (WHY HAVE TO RESET)

no other unique Raul...

and bingo "There must be the value for the next record in some place, but I never found out where"

anybody know? this is the only way you can be able to detect these before they happen.

Jay

On Fri, May 24, 2019 at 10:15 AM Raul Jager <raul@xxxxxxxxxx> wrote:

You can iterate over the "write" until you do not receive the
"duplicate record error". By repeating the write it will increment
the counter until it finds the proper value. (may be slow)

There must be the value for the next recor in some place, but I never
found out where.

Also, do you have other "unique index" over your table? The "duplicate"
may come from there.

On 5/24/19 9:56 AM, Jay Vaughn wrote:
no no no Raul... too late at the time with the WRITE.

Seems nobody knows how to detect them.

If you think it out, there has to be some "value" sitting somewhere
that
is
assigned to the ID when the write occurs.
BUT that column already exists in the table in an ID column... so
WHERE does that "value" sit to be used... or how is it determined to be used?
Is it participating somehow with the RRN?

probably a question for the IBM dB2 team, but thought I'd give the
forum
a
try.

Jay

On Fri, May 24, 2019 at 9:50 AM Raul Jager <raul@xxxxxxxxxx> wrote:

I will try to avoid the problem as first priority, to detect it you
can use an"error indicator" when you write in RPG or control the
return code in SQL.

On 5/24/19 9:37 AM, Jay Vaughn wrote:
what about my even better question Craig?

How to detect?

On Fri, May 24, 2019 at 9:32 AM Craig Richards
<craig@xxxxxxxxxxxxxxxx

wrote:

CPYF probably - it will keep ID from from_file and not increment
ID in to-file

On Fri, 24 May 2019 at 14:26, Jay Vaughn
<jeffersonvaughn@xxxxxxxxx>
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
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our
affiliate
link: https://amazon.midrange.com

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our
affiliate
link: https://amazon.midrange.com

-- Este e-mail fue enviado desde el Mail Server del diario ABC Color --
-- Verificado por Anti-Virus Corporativo Symantec --
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our
affiliate
link: https://amazon.midrange.com


-- Este e-mail fue enviado desde el Mail Server del diario ABC Color --
-- Verificado por Anti-Virus Corporativo Symantec --
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.