Hi
Iam using surrogate key stage in my job
surrogate stage as source
Trgt is seq file and In surrogate key i specified key type as
"source type=DB Sequence"
database DB2
In options i specified "Block Type= User Defined"
Its throwing fatal error and job is aborted..The following is the error..
DB2Driver Embedded SQL message: SQL0846N Invalid specification of an identity column or sequence object
"SEQUENCE" "SUITEADMIN.DB_SEQ". Reason code = "4". SQLSTATE=42815
sqlcode = -846;
sqlstate = 42815 [db2utils.C:228];
but when i specify as
"Block Type= System Defined"
Then its working well without throwing errors...(as usuall with gaps in surrogate key sequence)Why are we geting gaps and Why is this user specified block size not working....
Plz let me know the answers...
Thanks,
Rekha
Surrogate key stage with source type as DB Sequence
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 9
- Joined: Wed Feb 06, 2008 12:13 am
-
- Participant
- Posts: 9
- Joined: Wed Feb 06, 2008 12:13 am
Re: Surrogate key stage with source type as DB Sequence
This is my job structure....
Iam using surrogate key with no input and output
In Key source options
"Source Action property =Create "
"source type=DB Sequence"
"database= DB2
In options
"sequence block size = userdefined"
Its throwing fatal error and job is aborted..The following is the error..
DB2Driver Embedded SQL message: SQL0846N Invalid specification of an identity column or sequence object
"SEQUENCE" "SUITEADMIN.DB_SEQ". Reason code = "4". SQLSTATE=42815
sqlcode = -846;
sqlstate = 42815 [db2utils.C:228];
And when runing the job by changing
"sequence block size = System Picked"
Then its working well without throwing errors...(as usuall with gaps in surrogate key sequence when using ths db sequence in other jobs to insert values)Why are we geting gaps and Why is this user specified block size not working....
Plz let me know the full answers..
Thanks,
Rekha
Iam using surrogate key with no input and output
In Key source options
"Source Action property =Create "
"source type=DB Sequence"
"database= DB2
In options
"sequence block size = userdefined"
Its throwing fatal error and job is aborted..The following is the error..
DB2Driver Embedded SQL message: SQL0846N Invalid specification of an identity column or sequence object
"SEQUENCE" "SUITEADMIN.DB_SEQ". Reason code = "4". SQLSTATE=42815
sqlcode = -846;
sqlstate = 42815 [db2utils.C:228];
And when runing the job by changing
"sequence block size = System Picked"
Then its working well without throwing errors...(as usuall with gaps in surrogate key sequence when using ths db sequence in other jobs to insert values)Why are we geting gaps and Why is this user specified block size not working....
Plz let me know the full answers..
Thanks,
Rekha
Rekha - you don't need to completely repeat your first post. When I declare the stage with no inputs or outputs I do get that option, but that stage is only used to create the key, not to use it (if I understand the docs correctly).
Did you specify a block size of 1? Do you use a surrogate key stage in your job flow to actually generate keys?
Did you specify a block size of 1? Do you use a surrogate key stage in your job flow to actually generate keys?
-
- Participant
- Posts: 9
- Joined: Wed Feb 06, 2008 12:13 am
I cant see the whole solution...
I cant see the whole solution sent by you...I could see just 2 line...ArndW wrote:Rekha - you don't need to completely repeat your first post. When I declare the stage with no inputs or outputs I do get that option, but that stage is only used to create the key, not to use it (if I ...
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Premium membership will, among other benefits, let you see the entire posts of the five premium posters. Premium membership is inexpensive - less than 30c per day. All revenue from premium membership is allocated to defraying hosting and bandwidth costs incurred by DSXchange. So, by taking premium membership, you are not only gaining the benefits, you are also helping to keep DSXchange alive.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.