|
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?because
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 IDENTITYthat
(START WITH 1 INCREMENT BY 1)
primary key(id)
We all know that sometimes the identity column gets "out of whack" and
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"
beforehand.it was "out of whack"?bombs?
Is there a system table we can query to look at to detect these time
Abused google looking for an answer and everyone prides themselves withhow
to restart it... and never is it explained how to detect them
listTIAlist
jay
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
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
-- Este e-mail fue enviado desde el Mail Server del diario ABC Color --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
-- 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
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
