Anyone seen this error?
Moderators: chulett, rschirm, roy
-
- Premium Member
- Posts: 483
- Joined: Thu Jun 12, 2003 4:47 pm
- Location: St. Louis, Missouri USA
Anyone seen this error?
Example 1
LoadPartEffectivity..part_eff3.parts53: dsintbuf_getrow() - row has 887 columns when 16 expected
Example 2
LoadPartEffectivity..valid_parts.part_app11: dsintbuf_getrow() - row has 157 columns when 101 expected
This job has been running for a while with no changes (since April). Maybe goofy data?
Tony
LoadPartEffectivity..part_eff3.parts53: dsintbuf_getrow() - row has 887 columns when 16 expected
Example 2
LoadPartEffectivity..valid_parts.part_app11: dsintbuf_getrow() - row has 157 columns when 101 expected
This job has been running for a while with no changes (since April). Maybe goofy data?
Tony
Re: Anyone seen this error?
Goofy data :D ...
Ogmios
Ogmios
-
- Premium Member
- Posts: 483
- Joined: Thu Jun 12, 2003 4:47 pm
- Location: St. Louis, Missouri USA
Hi ,
We have also faced this problem while loading customer data , our source is comm seperated file customer file , some time we got comm "," character in address filed , this increase of no of column and job aborted at the time of loading .
If you have also this problem , open file and find out particular row value , and arrange to ractify source data .
Thanks
Arun Verma
We have also faced this problem while loading customer data , our source is comm seperated file customer file , some time we got comm "," character in address filed , this increase of no of column and job aborted at the time of loading .
If you have also this problem , open file and find out particular row value , and arrange to ractify source data .
Thanks
Arun Verma
Arun Verma
-
- Premium Member
- Posts: 483
- Joined: Thu Jun 12, 2003 4:47 pm
- Location: St. Louis, Missouri USA
-
- Participant
- Posts: 25
- Joined: Thu Oct 02, 2003 8:57 am
-
- Premium Member
- Posts: 483
- Joined: Thu Jun 12, 2003 4:47 pm
- Location: St. Louis, Missouri USA
Hello,
I recieved the same error today. I am running a multi instance job. And as tony pointed out , when i reran the job it went through just fine. The error message is given below.
dsintbuf_getrow() - row has 369 columns when 39 expected.
I am running on UNix (HP Super dome).
This error occurs randomly and in different jobs. Any inputs on the causes and solution will be really helpful.
Thanks,
Dhiraj
I recieved the same error today. I am running a multi instance job. And as tony pointed out , when i reran the job it went through just fine. The error message is given below.
dsintbuf_getrow() - row has 369 columns when 39 expected.
I am running on UNix (HP Super dome).
This error occurs randomly and in different jobs. Any inputs on the causes and solution will be really helpful.
Thanks,
Dhiraj
Are you sure your input data is correct. What usually happens is that e.g. you pick a ',' as seperator and some input field internally also contains a ','. This will lead DataStage to see more columns than actually were intended.
Ogmios
Ogmios
In theory there's no difference between theory and practice. In practice there is.
-
- Premium Member
- Posts: 483
- Joined: Thu Jun 12, 2003 4:47 pm
- Location: St. Louis, Missouri USA
I finally found that the problem was caused by using inter-process row buffering on the job. If you disable row buffering it will fix it (Ascential says v7.5 is fixed, but I haven't tested it). Oddly enough there's another bug in disabling row buffering, so it doesn't actually disable it. What I've found works is to select in-process row buffering and save the dialog (click OK), then open the Job Properties again and disable row buffering. If go from inter-process row buffering to disabling row buffering it won't work.
Tony
Tony
-
- Premium Member
- Posts: 483
- Joined: Thu Jun 12, 2003 4:47 pm
- Location: St. Louis, Missouri USA