QualityStage Job Error
-
- Premium Member
- Posts: 17
- Joined: Wed Jun 24, 2009 11:18 am
QualityStage Job Error
We are running into warning messages while running QualityStage jobs.
The exact warning message : External ustring too short. Imported only 0 external Characters into a ustring of fixed length 1. This is resulting in
thousands of records getting rejected.
We modified the Default field value from NULL to '' in a Sequencial File it helps in getting some of the rejected records through but still a significant number of records are in rejected state with the same error message.
Please help
Thanks
The exact warning message : External ustring too short. Imported only 0 external Characters into a ustring of fixed length 1. This is resulting in
thousands of records getting rejected.
We modified the Default field value from NULL to '' in a Sequencial File it helps in getting some of the rejected records through but still a significant number of records are in rejected state with the same error message.
Please help
Thanks
-
- Premium Member
- Posts: 425
- Joined: Sat Nov 19, 2005 9:26 am
- Location: New York City
- Contact:
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
If it's fixed length, then any default value must have the same number of characters as the field definition. Thus, for Char(1) - that is, ustring[1] - the default value "" is inappropriate - it must be " ".
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.
-
- Premium Member
- Posts: 17
- Joined: Wed Jun 24, 2009 11:18 am
Re: QualityStage Job Error
Hi,
Thanks a lot for your feedback. I tried changing all the fields with Char into Varchar it didnt help. All the records in the job were getting rejected with the same warning message.
I also tried changing default Null field value from '' to " " all the records were rejected with the same warning message
Another strange thing is that these jobs were running fine without any warnings previously 2 - 3 weeks back. However, now we are seeing this same warning message over and over again in multiple jobs with records getting rejected.
We did not apply any patch or make changes to these jobs
Thanks
Thanks a lot for your feedback. I tried changing all the fields with Char into Varchar it didnt help. All the records in the job were getting rejected with the same warning message.
I also tried changing default Null field value from '' to " " all the records were rejected with the same warning message
Another strange thing is that these jobs were running fine without any warnings previously 2 - 3 weeks back. However, now we are seeing this same warning message over and over again in multiple jobs with records getting rejected.
We did not apply any patch or make changes to these jobs
Thanks
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Premium Member
- Posts: 425
- Joined: Sat Nov 19, 2005 9:26 am
- Location: New York City
- Contact:
-
- Premium Member
- Posts: 17
- Joined: Wed Jun 24, 2009 11:18 am
Re: QualityStage Job Error
Hi,
We do have the previous jobs to compare against. Only thing that changed is, in the Extract job we changed the Null field value from NULL to empty string. We are suspecting that this is causing these warning messages in multiple subsequent jobs. We are running the extract job wihout any changes in Test environment to ensure that it is not causing the warning messages. I will update the post once it completes.
I couldnt APT_STRING_PADCHAR in the Administrative client under the Project. What is the significance of this?
Thanks
We do have the previous jobs to compare against. Only thing that changed is, in the Extract job we changed the Null field value from NULL to empty string. We are suspecting that this is causing these warning messages in multiple subsequent jobs. We are running the extract job wihout any changes in Test environment to ensure that it is not causing the warning messages. I will update the post once it completes.
I couldnt APT_STRING_PADCHAR in the Administrative client under the Project. What is the significance of this?
Thanks
-
- Premium Member
- Posts: 425
- Joined: Sat Nov 19, 2005 9:26 am
- Location: New York City
- Contact:
By default DS/QS used a null value(0x0) when extending or padding a string to a fixed length field (Char datatype), with this environment variable you can override the default value to any character. Most of the time you would like to use space(0x20)
You should find this env variable under Parallel category in the administrator tool
Did you try? let us know ...
You should find this env variable under Parallel category in the administrator tool
Did you try? let us know ...
Julio Rodriguez
ETL Developer by choice
"Sure we have lots of reasons for being rude - But no excuses
ETL Developer by choice
"Sure we have lots of reasons for being rude - But no excuses
-
- Premium Member
- Posts: 17
- Joined: Wed Jun 24, 2009 11:18 am
-
- Premium Member
- Posts: 17
- Joined: Wed Jun 24, 2009 11:18 am
-
- Premium Member
- Posts: 425
- Joined: Sat Nov 19, 2005 9:26 am
- Location: New York City
- Contact:
Did you type the metadata manually ... looks like you have different length .. now you have the inverse scenario... do a trim( ) on those fields having a warning or use same length in both input and output columns
Defining your column as Varchar avoid both scenarios ...
Defining your column as Varchar avoid both scenarios ...
Julio Rodriguez
ETL Developer by choice
"Sure we have lots of reasons for being rude - But no excuses
ETL Developer by choice
"Sure we have lots of reasons for being rude - But no excuses
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Premium Member
- Posts: 17
- Joined: Wed Jun 24, 2009 11:18 am
Hi,
Our testing finished with jobs were changes were not made and this time there were no warnings. However, the only change we made was in the Extract job - Changed the Null handler in the Sequential file from NULL to '' which resulted in all these warning messages.
When we reverted the changes back to Null the job finished successfully with no records getting rejected in another environment
I am still not clear why this only change would cause records getting rejected. Can you please suggest any documentation that I can refer to understand how data fields are handled by QualityStage?
Our issue is resolved. Thanks a lot for your help
Thanks
Our testing finished with jobs were changes were not made and this time there were no warnings. However, the only change we made was in the Extract job - Changed the Null handler in the Sequential file from NULL to '' which resulted in all these warning messages.
When we reverted the changes back to Null the job finished successfully with no records getting rejected in another environment
I am still not clear why this only change would cause records getting rejected. Can you please suggest any documentation that I can refer to understand how data fields are handled by QualityStage?
Our issue is resolved. Thanks a lot for your help
Thanks