invalid identifier
Moderators: chulett, rschirm, roy
invalid identifier
hi,
I run a job and it is aborted .It gives me the error message :" invalid identifier". Normally, it is because of either source or target table don't got such field. But I had checked and the field is existed in both source and target table ,and their data type,length also the same.
What else can cause this error occured?
Plz help.
I run a job and it is aborted .It gives me the error message :" invalid identifier". Normally, it is because of either source or target table don't got such field. But I had checked and the field is existed in both source and target table ,and their data type,length also the same.
What else can cause this error occured?
Plz help.
-
- Participant
- Posts: 3337
- Joined: Mon Jan 17, 2005 4:49 am
- Location: United Kingdom
-
- Participant
- Posts: 3337
- Joined: Mon Jan 17, 2005 4:49 am
- Location: United Kingdom
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Don't forget also to check any column name you might have typed (mis-typed) into a WHERE or other clause on the Selection tab. And also check that you have spelled the table name correctly (it, too, is an identifier).
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.
-
- Participant
- Posts: 3593
- Joined: Thu Jan 23, 2003 5:25 pm
- Location: Australia, Melbourne
- Contact:
Once again this looks like a SQL problem and you need to recheck your generated SQL statement. Is SEQNO a job parameter? Should it be #SEQNO#? Perhaps if you post your generated SQL on this thread we can debug it more quickly.
Certus Solutions
Blog: Tooling Around in the InfoSphere
Twitter: @vmcburney
LinkedIn:Vincent McBurney LinkedIn
Blog: Tooling Around in the InfoSphere
Twitter: @vmcburney
LinkedIn:Vincent McBurney LinkedIn
here is my previous question 's SQL statement :
INSERT INTO DMCHM_IB_RGB_DTL (LRECSEQNBR,LIBSEQNBR,NBENTYPE,STRDESGNCD,STRAGENTCD,DAMOUNT,DINTRATE,DTPERIODPROCESSTO,DTPERIODPROCESSFROM,DINTACCR,DTOTPREVBENAMOUNT,DCURRENTBALPAR,DCURRENTBALNPAR,DCURRENTBALLINK,DINTCURRENTPAR,DINTCURRENTNPAR,DINTCURRENTLINK,DPRVBALPAR,DPRVBALNPAR,DPRVBALLINK,DINTACCRUEDPAR,DINTACCRUEDLINK,DINTACCRUEDNPAR,PDS_UPDATED_DATE) VALUES (:1,:2,:3,:4,:5,:6,:7,TO_DATE(:8, 'YYYY-MM-DD HH24:MI:SS'),TO_DATE(:9, 'YYYY-MM-DD HH24:MI:SS'),:10,:11,:12,:13,:14,:15,:16,:17,:18,:19,:20,:21,:22,:23,TO_DATE(:24, 'YYYY-MM-DD HH24:MI:SS'));
UPDATE DMCHM_IB_RGB_DTL SET LIBSEQNBR=:2,NBENTYPE=:3,STRDESGNCD=:4,STRAGENTCD=:5,DAMOUNT=:6,DINTRATE=:7,DTPERIODPROCESSTO=TO_DATE(:8, 'YYYY-MM-DD HH24:MI:SS'),DTPERIODPROCESSFROM=TO_DATE(:9, 'YYYY-MM-DD HH24:MI:SS'),DINTACCR=:10,DTOTPREVBENAMOUNT=:11,DCURRENTBALPAR=:12,DCURRENTBALNPAR=:13,DCURRENTBALLINK=:14,DINTCURRENTPAR=:15,DINTCURRENTNPAR=:16,DINTCURRENTLINK=:17,DPRVBALPAR=:18,DPRVBALNPAR=:19,DPRVBALLINK=:20,DINTACCRUEDPAR=:21,DINTACCRUEDLINK=:22,DINTACCRUEDNPAR=:23,PDS_UPDATED_DATE=TO_DATE(:24, 'YYYY-MM-DD HH24:MI:SS') WHERE LRECSEQNBR=:1
plz help.
INSERT INTO DMCHM_IB_RGB_DTL (LRECSEQNBR,LIBSEQNBR,NBENTYPE,STRDESGNCD,STRAGENTCD,DAMOUNT,DINTRATE,DTPERIODPROCESSTO,DTPERIODPROCESSFROM,DINTACCR,DTOTPREVBENAMOUNT,DCURRENTBALPAR,DCURRENTBALNPAR,DCURRENTBALLINK,DINTCURRENTPAR,DINTCURRENTNPAR,DINTCURRENTLINK,DPRVBALPAR,DPRVBALNPAR,DPRVBALLINK,DINTACCRUEDPAR,DINTACCRUEDLINK,DINTACCRUEDNPAR,PDS_UPDATED_DATE) VALUES (:1,:2,:3,:4,:5,:6,:7,TO_DATE(:8, 'YYYY-MM-DD HH24:MI:SS'),TO_DATE(:9, 'YYYY-MM-DD HH24:MI:SS'),:10,:11,:12,:13,:14,:15,:16,:17,:18,:19,:20,:21,:22,:23,TO_DATE(:24, 'YYYY-MM-DD HH24:MI:SS'));
UPDATE DMCHM_IB_RGB_DTL SET LIBSEQNBR=:2,NBENTYPE=:3,STRDESGNCD=:4,STRAGENTCD=:5,DAMOUNT=:6,DINTRATE=:7,DTPERIODPROCESSTO=TO_DATE(:8, 'YYYY-MM-DD HH24:MI:SS'),DTPERIODPROCESSFROM=TO_DATE(:9, 'YYYY-MM-DD HH24:MI:SS'),DINTACCR=:10,DTOTPREVBENAMOUNT=:11,DCURRENTBALPAR=:12,DCURRENTBALNPAR=:13,DCURRENTBALLINK=:14,DINTCURRENTPAR=:15,DINTCURRENTNPAR=:16,DINTCURRENTLINK=:17,DPRVBALPAR=:18,DPRVBALNPAR=:19,DPRVBALLINK=:20,DINTACCRUEDPAR=:21,DINTACCRUEDLINK=:22,DINTACCRUEDNPAR=:23,PDS_UPDATED_DATE=TO_DATE(:24, 'YYYY-MM-DD HH24:MI:SS') WHERE LRECSEQNBR=:1
plz help.
-
- Participant
- Posts: 3593
- Joined: Thu Jan 23, 2003 5:25 pm
- Location: Australia, Melbourne
- Contact:
Since the word SEQNO does not appear anywhere in your SQL statement it may be appearing in one of your bound columns as a piece of text. You might have a transformer derivation that is setting your sequence number field to the word SEQNO instead of a numeric value.
Try doing a database trace while the job is running to capture the exact SQL statement.
Try doing a database trace while the job is running to capture the exact SQL statement.
Certus Solutions
Blog: Tooling Around in the InfoSphere
Twitter: @vmcburney
LinkedIn:Vincent McBurney LinkedIn
Blog: Tooling Around in the InfoSphere
Twitter: @vmcburney
LinkedIn:Vincent McBurney LinkedIn
You might also let us know where the error is being generated. Are you using Custom Sql in any of your stages? That kind of error generally comes from improperly formatted custom sql more than any generated sql like the 'Insert then Update' example you posted.
How about your source stage?
How about your source stage?
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers