Hi
i am loading data in to DB2/AIX64.
My source data is CSV file. My targe table has primary key.When i ran the job i am getting data with warnings.
any one resolve this please.....
Warning:
Source_data,0: Field "column_Index" has import error and no default value; data: {N U L L}, at offset: 123
Cheers
Sreddy
null and duplicate
Moderators: chulett, rschirm, roy
sreddy,
Seems your data has some null values fot the field 'column_Index' but in the source metadata you might have explicity made those fields as NotNull. If you have used it correctly, the only reason would be source and metadata mismatch.
And, as Craig said, there are lot number of posts where this issue was discussed earlier.
Seems your data has some null values fot the field 'column_Index' but in the source metadata you might have explicity made those fields as NotNull. If you have used it correctly, the only reason would be source and metadata mismatch.
And, as Craig said, there are lot number of posts where this issue was discussed earlier.
Thanks and Regards!!
dspxlearn
dspxlearn
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Why don't people read the messages?!!
From Source_data (on partition #0 as it happens) a row has been read that contains the characters "NULL" in positions 123-126. Presumably this is one of the fields defined in the record schema. This field needs to have its Null Field Value property set to "NULL" and, optionally, a Default value set with which to replace the null.
Just for interest, the curly braces are DataStage's way of reporting a raw string. Non-printable characters are printed as two-digit (or four-digit) hexadecimal representations, for example {J O H N 09 S M I T H}.
![Rolling Eyes :roll:](./images/smilies/icon_rolleyes.gif)
From Source_data (on partition #0 as it happens) a row has been read that contains the characters "NULL" in positions 123-126. Presumably this is one of the fields defined in the record schema. This field needs to have its Null Field Value property set to "NULL" and, optionally, a Default value set with which to replace the null.
Just for interest, the curly braces are DataStage's way of reporting a raw string. Non-printable characters are printed as two-digit (or four-digit) hexadecimal representations, for example {J O H N 09 S M I T H}.
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.
duplicates
Hi All
i used default value for all columns at source sequential file metadata, then ran the job.
Job is successfully completed. 17 records are not inserted.
I assumed those are duplicates. Bucause in target i have Primary key.
I found below:
Trg_stage,0: Warning: jobname.Trg_stage: This update action 'update or insert' is not compatible with parameter array binding. Array Size property will be set to 1.
suggested me.
cheers...
SReddy
i used default value for all columns at source sequential file metadata, then ran the job.
Job is successfully completed. 17 records are not inserted.
I assumed those are duplicates. Bucause in target i have Primary key.
I found below:
Trg_stage,0: Warning: jobname.Trg_stage: This update action 'update or insert' is not compatible with parameter array binding. Array Size property will be set to 1.
suggested me.
cheers...
SReddy
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
That is a completely different issue and warrants a separate search and/or thread.
Your original issue (the occurrence of "NULL" in your data) appears to have been resolved. Please mark this thread accordingly.
Your original issue (the occurrence of "NULL" in your data) appears to have been resolved. Please mark this thread accordingly.
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.