Problem viewing the data

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
devsonali
Premium Member
Premium Member
Posts: 155
Joined: Sun Mar 18, 2007 2:31 pm

Problem viewing the data

Post by devsonali »

Hi everybody

I have problem accessing the a seq file

Here is the job

SEQFILEINPUT -- > AGGREGATOR --> SEQFILEOUTPUT

My input has three columns X,Y,Z
with data looking like this (comma delimiter)
22,44,66
234,344,2222
345,456,7980
For some reason when I view data it gives me only last row ?
What can be the problem ?

Thanks
us1aslam1us
Charter Member
Charter Member
Posts: 822
Joined: Sat Sep 17, 2005 5:25 pm
Location: USA

Post by us1aslam1us »

What format properties are you using?
I haven't failed, I've found 10,000 ways that don't work.
Thomas Alva Edison(1847-1931)
devsonali
Premium Member
Premium Member
Posts: 155
Joined: Sun Mar 18, 2007 2:31 pm

Post by devsonali »

Record level
Final Delimiter = end (I this one with whitespace and none)
Field Defaults
Delimiter = commas
Quote= double (tried it with None as well )
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Post by ArndW »

Are you viewing the data in the output sequential stage? If so, perhaps your aggregator only output one row?
devsonali
Premium Member
Premium Member
Posts: 155
Joined: Sun Mar 18, 2007 2:31 pm

Post by devsonali »

Actually I was looking at input stage "View Data" .
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Post by ArndW »

Have you set your view data options to limit to 1 row?
us1aslam1us
Charter Member
Charter Member
Posts: 822
Joined: Sat Sep 17, 2005 5:25 pm
Location: USA

Post by us1aslam1us »

You need to define the record delimiter property. Check what process is generating the input file and are you able to view the file properly outside datastage.
I haven't failed, I've found 10,000 ways that don't work.
Thomas Alva Edison(1847-1931)
devsonali
Premium Member
Premium Member
Posts: 155
Joined: Sun Mar 18, 2007 2:31 pm

Post by devsonali »

ArndW wrote:Have you set your view data options to limit to 1 row? ...
No
devsonali
Premium Member
Premium Member
Posts: 155
Joined: Sun Mar 18, 2007 2:31 pm

Post by devsonali »

us1aslam1us wrote:You need to define the record delimiter property.

Check what process is generating the input file and are you able to view the file properly outside datastage.
Input file was manually created and I am able to view it outside datastage.
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Post by ArndW »

If you only see one row, does it contain just the data for the first row in the correct format? Have you set your final delimiter to <cr>?
Zhang Bo
Participant
Posts: 15
Joined: Sun Jul 15, 2007 9:22 pm

Post by Zhang Bo »

the sequential file you generated manually is different from using datastage when your ds server is Unix,i guess you must generate it in windows then transfer to Unix,that makes the different.if you directly generate it in unix,the file can be the same with datastage generated.you can compare the file you generated manually with datastage does in hex mode,you can see the file from Windows contain an additional x'0D' before x'0A',unix file only contains x'0A'.and i think if you choose Final Delimiter = none and Quote = none(if you really didn't add quote in the sequential file you generated),that will make you see all data
MaDFroG
devsonali
Premium Member
Premium Member
Posts: 155
Joined: Sun Mar 18, 2007 2:31 pm

Post by devsonali »

ArndW wrote:If you only see one row, does it contain just the data for the first row in the correct format? Have you set your final delimiter to <cr>? ...
It shows me only the last row on the file . Final delimiter is set to end . What is <CR> ?
devsonali
Premium Member
Premium Member
Posts: 155
Joined: Sun Mar 18, 2007 2:31 pm

Post by devsonali »

Zhang Bo wrote:the sequential file you generated manually is different from using datastage when your ds server is Unix,i guess you must generate it in windows then transfer to Unix,that makes the different.if you directly generate it in unix,the file can be the same with datastage generated.you can compare the file you generated manually with datastage does in hex mode,you can see the file from Windows contain an additional x'0D' before x'0A',unix file only contains x'0A'.and i think if you choose Final Delimiter = none and Quote = none(if you really didn't add quote in the sequential file you generated),that will make you see all data
I generated the text file in windows and trasferred it to the unix server .

Also when I use quote and Final Delimiter as none it gives me the following error
Error executing view data command
import validation failed .
devsonali
Premium Member
Premium Member
Posts: 155
Joined: Sun Mar 18, 2007 2:31 pm

Post by devsonali »

Enabling the record delimiter property to DOS fixes the problem ,but I still don t understand the reason for this

Thanks
us1aslam1us
Charter Member
Charter Member
Posts: 822
Joined: Sat Sep 17, 2005 5:25 pm
Location: USA

Post by us1aslam1us »

Your answer lies here:
I generated the text file in windows and trasferred it to the unix server .
[/code]
I haven't failed, I've found 10,000 ways that don't work.
Thomas Alva Edison(1847-1931)
Post Reply