×
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.
Your Sync_Identity_Counter script works perfectly. I still don't understand why I have to run it, but it solves the problem.
I used this to generate a script on ALL tables with identity columns:
SELECT 'CALL Sync_Identity_Counter(''' || TRIM(SYSTEM_TABLE_SCHEMA) || ''',''' || TRIM(SYSTEM_TABLE_NAME) || ''');'
FROM qsys2.SYSCOLUMNS
WHERE IS_IDENTITY='YES' AND SYSTEM_TABLE_SCHEMA IN ('schema1','schema2')
Matt
From: Matt Olson
Sent: Tuesday, December 4, 2018 1:18 PM
To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxx>
Subject: Identity column re-using existing numbers?
We migrated some of our tables to another partition for testing and we have noticed that their identity columns which should generate the next available number is infact generating an existing number and failing the primary key check. Has anyone see this before?
There some easy command to restart identity value to the next available number?
We are mystified why this didn't come over during the restore of that file...
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
