IDENTITY COLUMNS

M Vo

IDENTITY COLUMNS
2007-10-17 09:47:14 (F-Secure Anti-Virus 7.20
migrating these tables from source, data are also copied. Is there any easy
way to determine the last value assigned to the identity column on the source
so that we can properly set the starting value on target prior to data load?
We'd like to automate this process if possible, therefore we don't want to
manually issue INSERT then SELECT IDENTITY_VAL_LOCAL every time for
every table.

Thanks

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Mark Vickers

Re: IDENTITY COLUMNS
(in response to M Vo)
Mai,
The rules have changed from v7 to v8 to v9 - what platform and what
version of DB2 ?
Mark.



M Vo <[login to unmask email]>
Sent by: DB2 Data Base Discussion List <[login to unmask email]>
10/17/2007 09:05 AM
Please respond to
DB2 Database Discussion list at IDUG <[login to unmask email]>


To
[login to unmask email]
cc

Subject
IDENTITY COLUMNS






2007-10-17 09:47:14 (F-Secure Anti-Virus 7.20
migrating these tables from source, data are also copied. Is there any
easy
way to determine the last value assigned to the identity column on the
source
so that we can properly set the starting value on target prior to data
load?
We'd like to automate this process if possible, therefore we don't want to

manually issue INSERT then SELECT IDENTITY_VAL_LOCAL every time for
every table.

Thanks

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and
home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page
select "Join or Leave the list". The IDUG DB2-L FAQ is at
http://www.idugdb2-l.org. The IDUG List Admins can be reached at
[login to unmask email] Find out the latest on IDUG conferences
at http://conferences.idug.org/index.cfm





This e-mail (and any attachments) may contain information that is
confidential and/or protected by law. Any review, use, distribution or
disclosure to anyone other than the
intended recipient(s) is strictly prohibited. If you are not the intended
recipient, please contact the sender by reply email and delete all copies
of this message.



---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Pradeep Gunjala

Re: IDENTITY COLUMNS
(in response to Mark Vickers)
Are you looking for a query some thing like this.

SELECT B.MAXASSIGNEDVAL AS "LAST ASSIGNED VAL"
FROM SYSIBM.SYSSEQUENCESDEP A,
SYSIBM.SYSSEQUENCES B
WHERE A.BSEQUENCEID = B.SEQUENCEID
AND B.SEQTYPE = 'I'
AND A.DCREATOR = 'XYZ'
AND A.DNAME IN ('ABC');

Change XYZ to your database creator name and ABC to Identity column table
name.

Thanks,
Pradeep




M Vo <[login to unmask email]>
Sent by: DB2 Data Base Discussion List <[login to unmask email]>
10/17/2007 10:03 AM
Please respond to
DB2 Database Discussion list at IDUG <[login to unmask email]>


To
[login to unmask email]
cc

Subject
[DB2-L] IDENTITY COLUMNS






2007-10-17 09:47:14 (F-Secure Anti-Virus 7.20
migrating these tables from source, data are also copied. Is there any
easy
way to determine the last value assigned to the identity column on the
source
so that we can properly set the starting value on target prior to data
load?
We'd like to automate this process if possible, therefore we don't want to

manually issue INSERT then SELECT IDENTITY_VAL_LOCAL every time for
every table.

Thanks

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and
home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page
select "Join or Leave the list". The IDUG DB2-L FAQ is at
http://www.idugdb2-l.org. The IDUG List Admins can be reached at
[login to unmask email] Find out the latest on IDUG conferences
at http://conferences.idug.org/index.cfm


---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

David Churn

Re: IDENTITY COLUMNS
(in response to Pradeep Gunjala)
M,

Are you on DB2 version 8?

If yes, you can issue an INSERT within SELECT to get your value. And if you
are using multi-row INSERT you can also use multi-row SELECT with that. It
would be something like;

SELECT IDENTITY_ID
FROM FINAL TABLE
( INSERT some stuff )
ORDER BY INPUT SEQUENCE <--- necessary only for multi-row function

--
David Churn
Database Architect, DST Systems
President, Heart of America DB2 Users Group

On 10/17/07, M Vo <[login to unmask email]> wrote:
>
> 2007-10-17 09:47:14 (F-Secure Anti-Virus 7.20
> migrating these tables from source, data are also copied. Is there any
> easy
> way to determine the last value assigned to the identity column on the
> source
> so that we can properly set the starting value on target prior to data
> load?
> We'd like to automate this process if possible, therefore we don't want to
> manually issue INSERT then SELECT IDENTITY_VAL_LOCAL every time for
> every table.
>
> Thanks
>
>
> ---------------------------------------------------------------------------------
> Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and
> home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page
> select "Join or Leave the list". The IDUG DB2-L FAQ is at
> http://www.idugdb2-l.org. The IDUG List Admins can be reached at
> [login to unmask email] Find out the latest on IDUG conferences
> at http://conferences.idug.org/index.cfm

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

M Vo

Re: IDENTITY COLUMNS
(in response to David Churn)
Yes, the SQL is EXACTLY what I was looking for. Thanks very much.

BTW we're still V7, going on V8 by end of 2007.

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

[login to unmask email]

Re: IDENTITY COLUMNS
(in response to M Vo)
Dear Sir/ Madam,

Kindly remove my name from your listers as I am not the part of it and
contineously getting these unwanted mails.



Thanks & Regards,
Anuj Mathur
SSM
9829063665



"M Vo" <[login to unmask email]>
Sent by: "DB2 Data Base Discussion List" <[login to unmask email]>
10/22/2007 10:15 PM
Please respond to
"DB2 Database Discussion list at IDUG" <[login to unmask email]>


To
[login to unmask email]
cc

Subject
Re: [DB2-L] IDENTITY COLUMNS






Yes, the SQL is EXACTLY what I was looking for. Thanks very much.

BTW we're still V7, going on V8 by end of 2007.

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and
home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page
select "Join or Leave the list". The IDUG DB2-L FAQ is at
http://www.idugdb2-l.org. The IDUG List Admins can be reached at
[login to unmask email] Find out the latest on IDUG conferences
at http://conferences.idug.org/index.cfm



The information contained in this message may be CONFIDENTIAL and is for the intended addressee only. Any unauthorized use, dissemination of the information, or copying of this message is prohibited. If you are not the intended addressee, please notify the sender immediately and delete this message.

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Angela Cheong

identity columns
(in response to amathur@METLIFE.COM)
We are preparing to move some tables into production using identity
column as a primary key (generated always). I'm trying to work out the
details of loading/unloading this data from one subsystem to another.
I'm trying to use the IDENTITYOVERRIDE parameter, but keep getting an
error stating the column itself is not recognized.



From the utility guide: To load the unloaded identity column data, add
the IDENTITYOVERRIDE keyword to the LOAD control statement. Change the
dummy field name, DSN_IDENTITY, to the corresponding identity column
name in the target table.





Seems simple enough, but ....? Has anyone used this successfully?
Can you provide an example?



Thanks.





Angela Cheong


**************************************************************************************************
Note:
The information contained in this message may be privileged and confidential and
protected from disclosure. If the reader of this message is not the intended
recipient, or an employee or agent responsible for delivering this message to
the intended recipient, you are hereby notified that any dissemination,
distribution or copying of this communication is strictly prohibited. If you
have received this communication in error, please notify us immediately by
replying to the message and deleting it from your computer.
**************************************************************************************************

The IDUG DB2-L Listserv is only part of your membership in IDUG. DB2-L list archives, the FAQ, and delivery preferences are at http://www.idug.org/lsidug under the Listserv tab. While at the site, you can also access the IDUG Online Learning Center, Tech Library and Code Place, see the latest IDUG conference information, and much more. If you have not yet signed up for Basic Membership in IDUG, available at no cost, click on Member Services at http://www.idug.org/lsms

Tim R Ohling

Re: identity columns
(in response to Angela Cheong)
Since the guy that requested this feature is on vacation this week,
here's an example. The identity column is the table_ID (in this case a
smallint):

LOAD DATA INDDN SYSREC01
RESUME NO REPLACE STATISTICS TABLE(ALL) INDEX(ALL) LOG NO
NOCOPYPEND SORTKEYS 86 IDENTITYOVERRIDE
EBCDIC CCSID(0037)

INTO TABLE owner.table_nm
(
table_ID
POSITION ( 1 ) SMALLINT
,
next_attribute
POSITION ( 3 ) CHAR ( 8 )
,
etc_attribute
POSITION ( 11 ) CHAR ( 8 )

)

HTH,
Tim
________________________________

From: DB2 Data Base Discussion List [mailto:[login to unmask email] On
Behalf Of Cheong, Angela
Sent: Friday, December 28, 2007 8:20 AM
To: [login to unmask email]
Subject: [DB2-L] identity columns



We are preparing to move some tables into production using identity
column as a primary key (generated always). I'm trying to work out the
details of loading/unloading this data from one subsystem to another.
I'm trying to use the IDENTITYOVERRIDE parameter, but keep getting an
error stating the column itself is not recognized.



From the utility guide: To load the unloaded identity column data, add
the IDENTITYOVERRIDE keyword to the LOAD control statement. Change the
dummy field name, DSN_IDENTITY, to the corresponding identity column
name in the target table.





Seems simple enough, but ....? Has anyone used this successfully?
Can you provide an example?



Thanks.





Angela Cheong


************************************************************************
**************************
Note:
The information contained in this message may be privileged and
confidential and
protected from disclosure. If the reader of this message is not the
intended
recipient, or an employee or agent responsible for delivering this
message to
the intended recipient, you are hereby notified that any dissemination,
distribution or copying of this communication is strictly prohibited. If
you
have received this communication in error, please notify us immediately
by
replying to the message and deleting it from your computer.
************************************************************************
**************************

The IDUG DB2-L Listserv is only part of your membership in IDUG. DB2-L
list archives, the FAQ, and delivery preferences are at www.idug.org
< http://www.idug.org/lsidug > under the Listserv tab. While at the site,
you can also access the IDUG Online Learning Center, Tech Library and
Code Place, see the latest IDUG conference information
< http://www.idug.org/lsconf > , and much more.
If you have not yet signed up for Basic Membership in IDUG, available at
no cost, click on Member Services < http://www.idug.org/lsms >

The IDUG DB2-L Listserv is only part of your membership in IDUG. DB2-L list archives, the FAQ, and delivery preferences are at http://www.idug.org/lsidug under the Listserv tab. While at the site, you can also access the IDUG Online Learning Center, Tech Library and Code Place, see the latest IDUG conference information, and much more. If you have not yet signed up for Basic Membership in IDUG, available at no cost, click on Member Services at http://www.idug.org/lsms

David Seibert

Re: identity columns
(in response to Tim R Ohling)
Hi Angela,

Which version of DB2 are you using?

If you are not at v8 at least, I suggest you will still have problems.
I have not tried the technique you describe.
But if it succeeds, you still have the issue of the STARTWITH value.
If you have 10,000 rows in your source table and your target table on
the other subsystem is newly created, in addition to the steps you
describe, you need to create the table with a STARTWITH value of 10001.
Otherwise your next insert after the load will attempt to use 1 as the
column value (or whatever your STARTWITH value is).

With version 8, everything is simpler. You can alter the GENERATED
clause value from ALWAYS to BY DEFAULT and back to do the load.
You can also alter the STARTWITH value and not have to modify the
original DDL.

Dave
The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.

The IDUG DB2-L Listserv is only part of your membership in IDUG. DB2-L list archives, the FAQ, and delivery preferences are at http://www.idug.org/lsidug under the Listserv tab. While at the site, you can also access the IDUG Online Learning Center, Tech Library and Code Place, see the latest IDUG conference information, and much more. If you have not yet signed up for Basic Membership in IDUG, available at no cost, click on Member Services at http://www.idug.org/lsms

Angela Cheong

Re: identity columns
(in response to David Seibert)
Thank you, that worked.

I was following the utility guide and putting the IDENTITYOVERRIDE parm
in the INTO TABLE spec, like this:

INTO TABLE tablename IDENTITYOVERRIDE (chapter 16 page 207 of Utility
Guide).


Angela Cheong


-----Original Message-----
From: DB2 Data Base Discussion List [mailto:[login to unmask email] On
Behalf Of Ohling, Tim R
Sent: Friday, December 28, 2007 10:46 AM
To: [login to unmask email]
Subject: Re: [DB2-L] identity columns

Since the guy that requested this feature is on vacation this week,
here's an example. The identity column is the table_ID (in this case a
smallint):

LOAD DATA INDDN SYSREC01
RESUME NO REPLACE STATISTICS TABLE(ALL) INDEX(ALL) LOG NO
NOCOPYPEND SORTKEYS 86 IDENTITYOVERRIDE
EBCDIC CCSID(0037)

INTO TABLE owner.table_nm
(
table_ID
POSITION ( 1 ) SMALLINT
,
next_attribute
POSITION ( 3 ) CHAR ( 8 )
,
etc_attribute
POSITION ( 11 ) CHAR ( 8 )

)

HTH,
Tim
________________________________

From: DB2 Data Base Discussion List [mailto:[login to unmask email] On
Behalf Of Cheong, Angela
Sent: Friday, December 28, 2007 8:20 AM
To: [login to unmask email]
Subject: [DB2-L] identity columns



We are preparing to move some tables into production using identity
column as a primary key (generated always). I'm trying to work out the
details of loading/unloading this data from one subsystem to another.
I'm trying to use the IDENTITYOVERRIDE parameter, but keep getting an
error stating the column itself is not recognized.



From the utility guide: To load the unloaded identity column data, add
the IDENTITYOVERRIDE keyword to the LOAD control statement. Change the
dummy field name, DSN_IDENTITY, to the corresponding identity column
name in the target table.





Seems simple enough, but ....? Has anyone used this successfully?
Can you provide an example?



Thanks.





Angela Cheong


************************************************************************
**************************
Note:
The information contained in this message may be privileged and
confidential and
protected from disclosure. If the reader of this message is not the
intended
recipient, or an employee or agent responsible for delivering this
message to
the intended recipient, you are hereby notified that any dissemination,
distribution or copying of this communication is strictly prohibited. If
you
have received this communication in error, please notify us immediately
by
replying to the message and deleting it from your computer.
************************************************************************
**************************

The IDUG DB2-L Listserv is only part of your membership in IDUG. DB2-L
list archives, the FAQ, and delivery preferences are at www.idug.org
< http://www.idug.org/lsidug > under the Listserv tab. While at the site,
you can also access the IDUG Online Learning Center, Tech Library and
Code Place, see the latest IDUG conference information
< http://www.idug.org/lsconf > , and much more.
If you have not yet signed up for Basic Membership in IDUG, available at
no cost, click on Member Services < http://www.idug.org/lsms >

The IDUG DB2-L Listserv is only part of your membership in IDUG. DB2-L
list archives, the FAQ, and delivery preferences are at
http://www.idug.org/lsidug under the Listserv tab. While at the site,
you can also access the IDUG Online Learning Center, Tech Library and
Code Place, see the latest IDUG conference information, and much more.
If you have not yet signed up for Basic Membership in IDUG, available at
no cost, click on Member Services at http://www.idug.org/lsms

**************************************************************************************************
Note:
The information contained in this message may be privileged and confidential and
protected from disclosure. If the reader of this message is not the intended
recipient, or an employee or agent responsible for delivering this message to
the intended recipient, you are hereby notified that any dissemination,
distribution or copying of this communication is strictly prohibited. If you
have received this communication in error, please notify us immediately by
replying to the message and deleting it from your computer.
**************************************************************************************************

The IDUG DB2-L Listserv is only part of your membership in IDUG. DB2-L list archives, the FAQ, and delivery preferences are at http://www.idug.org/lsidug under the Listserv tab. While at the site, you can also access the IDUG Online Learning Center, Tech Library and Code Place, see the latest IDUG conference information, and much more. If you have not yet signed up for Basic Membership in IDUG, available at no cost, click on Member Services at http://www.idug.org/lsms

Angela Cheong

Re: identity columns
(in response to Angela Cheong)
Dave,

We are at version 8. This is the information I was looking for. I was
able to get the load to work with the IDENTITYOVERRIDE using a GENERATED
ALWAYS column definition (thanks to Tim). Now having done that, I
should just be able to alter the STARTWITH on my target table, correct?
Thank you for your help.



Angela

From: DB2 Data Base Discussion List [mailto:[login to unmask email] On
Behalf Of Seibert, Dave
Sent: Friday, December 28, 2007 11:00 AM
To: [login to unmask email]
Subject: Re: [DB2-L] identity columns



Hi Angela,



Which version of DB2 are you using?



If you are not at v8 at least, I suggest you will still have problems.

I have not tried the technique you describe.

But if it succeeds, you still have the issue of the STARTWITH value.

If you have 10,000 rows in your source table and your target table on
the other subsystem is newly created, in addition to the steps you
describe, you need to create the table with a STARTWITH value of 10001.
Otherwise your next insert after the load will attempt to use 1 as the
column value (or whatever your STARTWITH value is).



With version 8, everything is simpler. You can alter the GENERATED
clause value from ALWAYS to BY DEFAULT and back to do the load.

You can also alter the STARTWITH value and not have to modify the
original DDL.

Dave


**************************************************************************************************
Note:
The information contained in this message may be privileged and confidential and
protected from disclosure. If the reader of this message is not the intended
recipient, or an employee or agent responsible for delivering this message to
the intended recipient, you are hereby notified that any dissemination,
distribution or copying of this communication is strictly prohibited. If you
have received this communication in error, please notify us immediately by
replying to the message and deleting it from your computer.
**************************************************************************************************

The IDUG DB2-L Listserv is only part of your membership in IDUG. DB2-L list archives, the FAQ, and delivery preferences are at http://www.idug.org/lsidug under the Listserv tab. While at the site, you can also access the IDUG Online Learning Center, Tech Library and Code Place, see the latest IDUG conference information, and much more. If you have not yet signed up for Basic Membership in IDUG, available at no cost, click on Member Services at http://www.idug.org/lsms

Raey

Re: identity columns
(in response to Angela Cheong)
Angela,

You can issue rest start with command... look the syntax in the Admin Guide. I believe there is a topic in the admin guide on How to load tables with identify column
Regards,
Ayalew.


"Cheong, Angela" <[login to unmask email]> wrote:
Dave,
We are at version 8. This is the information I was looking for. I was able to get the load to work with the IDENTITYOVERRIDE using a GENERATED ALWAYS column definition (thanks to Tim). Now having done that, I should just be able to alter the STARTWITH on my target table, correct? Thank you for your help.

Angela

From: DB2 Data Base Discussion List [mailto:[login to unmask email] On Behalf Of Seibert, Dave
Sent: Friday, December 28, 2007 11:00 AM
To: [login to unmask email]
Subject: Re: [DB2-L] identity columns



Hi Angela,

Which version of DB2 are you using?

If you are not at v8 at least, I suggest you will still have problems.
I have not tried the technique you describe.
But if it succeeds, you still have the issue of the STARTWITH value.
If you have 10,000 rows in your source table and your target table on the other subsystem is newly created, in addition to the steps you describe, you need to create the table with a STARTWITH value of 10001. Otherwise your next insert after the load will attempt to use 1 as the column value (or whatever your STARTWITH value is).



With version 8, everything is simpler. You can alter the GENERATED clause value from ALWAYS to BY DEFAULT and back to do the load.

You can also alter the STARTWITH value and not have to modify the original DDL.

Dave



**************************************************************************************************
Note:
The information contained in this message may be privileged and confidential and
protected from disclosure. If the reader of this message is not the intended
recipient, or an employee or agent responsible for delivering this message to
the intended recipient, you are hereby notified that any dissemination,
distribution or copying of this communication is strictly prohibited. If you
have received this communication in error, please notify us immediately by
replying to the message and deleting it from your computer.
**************************************************************************************************

The IDUG DB2-L Listserv is only part of your membership in IDUG. DB2-L list archives, the FAQ, and delivery preferences are at www.idug.org under the Listserv tab. While at the site, you can also access the IDUG Online Learning Center, Tech Library and Code Place, see the latest IDUG conference information, and much more.
If you have not yet signed up for Basic Membership in IDUG, available at no cost, click on Member Services


---------------------------------
Looking for last minute shopping deals? Find them fast with Yahoo! Search.

The IDUG DB2-L Listserv is only part of your membership in IDUG. DB2-L list archives, the FAQ, and delivery preferences are at http://www.idug.org/lsidug under the Listserv tab. While at the site, you can also access the IDUG Online Learning Center, Tech Library and Code Place, see the latest IDUG conference information, and much more. If you have not yet signed up for Basic Membership in IDUG, available at no cost, click on Member Services at http://www.idug.org/lsms

David Seibert

Re: identity columns
(in response to Raey)
Yes Angela,
You can alter the start with value on your target table.

Here is the actual syntax:

ALTER TABLE STAFFI
ALTER COLUMN ID
RESTART WITH 10001

The SQL Reference provides the full syntax and description.

Note that you can just specify

ALTER TABLE STAFFI
ALTER COLUMN ID
RESTART

And the start with value will revert to the original value specified
when the column was created.

While we are on the topic, you may wish to look up the SEQUENCE object
to see how that behaves differently.


Dave




The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.


From: DB2 Data Base Discussion List [mailto:[login to unmask email] On
Behalf Of Cheong, Angela
Sent: Friday, December 28, 2007 12:58 PM
To: [login to unmask email]
Subject: Re: [DB2-L] identity columns



Dave,

We are at version 8. This is the information I was looking for. I was
able to get the load to work with the IDENTITYOVERRIDE using a GENERATED
ALWAYS column definition (thanks to Tim). Now having done that, I
should just be able to alter the STARTWITH on my target table, correct?
Thank you for your help.



Angela

The IDUG DB2-L Listserv is only part of your membership in IDUG. DB2-L list archives, the FAQ, and delivery preferences are at http://www.idug.org/lsidug under the Listserv tab. While at the site, you can also access the IDUG Online Learning Center, Tech Library and Code Place, see the latest IDUG conference information, and much more. If you have not yet signed up for Basic Membership in IDUG, available at no cost, click on Member Services at http://www.idug.org/lsms