RE: Problem with GENERATED ALWAYS Identity column

["Wilt, Charles" <CWilt@xxxxxxxxxxxx>]

As far as detail in the joblog, the duplicate key message included the RRN of 
the record with the duplicate key.....

Hey, as I think about this, I realize that the RRN it gave went up 1 with every 
attempt (1,2,3,4,5,6,...); assuming that I'm recalling correctly.

If so, seems to be more evidence that the "next identity value to use" was 
somehow reset or maybe corrupted.  FYI: I didn't do it an nobody else would 
know how ;-)


As far as duplicating the problem.  The way this file came into existence was 
as follows.

--Originally defined with DDS as a non-keyed physical.
--Retrieved SQL source using iSeries Nav.
--Modified source as needed (ie. create table RECNAME, rename table RECNAME 
TABLENAME for RPG)
--Added new column DHDOID, as GENERATED ALWAYS as IDENTITY.
--Added PRIMARY KEY DHDOID
--Renamed original file
--Created SQL Table
--CPYF MBROPT(*REPLACE) FMTOPT(*MAP *DROP) from saved version to new.

Again, this was within our CMS, so most of the above was done automatically 
behind the scenes.
After the promote, the old records where in the file and the IDENTITY column 
value started at 1 and when thru about 17,000.

This was almost 3 months ago that the file was converted to a table with the 
primary key being the new GENERATED ALWAYS as IDENTITY column.

Again, the file exists in multiple libraries, only one copy seems to have had 
the problem.


Very weird...
 

Charles Wilt
--
iSeries Systems Administrator / Developer
Mitsubishi Electric Automotive America
ph: 513-573-4343
fax: 513-398-1121
 

> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx
> [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of rob@xxxxxxxxx
> Sent: Wednesday, August 03, 2005 12:50 PM
> To: Midrange Systems Technical Discussion
> Subject: Re: Problem with GENERATED ALWAYS Identity column
> 
> 
> Was there any detail in the joblog?
> 
> I tried to duplicate this by creating a table, stuffing data 
> into it, and 
> then changing an existing INT field to an identity column but haven't 
> figured out how.
> 
> Rob Berendt
> --