Page 1 of 1

Problem viewing the data

Posted: Tue Jul 24, 2007 3:20 pm
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

Posted: Tue Jul 24, 2007 3:23 pm
by us1aslam1us
What format properties are you using?

Posted: Tue Jul 24, 2007 3:29 pm
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 )

Posted: Tue Jul 24, 2007 3:36 pm
by ArndW
Are you viewing the data in the output sequential stage? If so, perhaps your aggregator only output one row?

Posted: Tue Jul 24, 2007 3:40 pm
by devsonali
Actually I was looking at input stage "View Data" .

Posted: Tue Jul 24, 2007 3:46 pm
by ArndW
Have you set your view data options to limit to 1 row?

Posted: Tue Jul 24, 2007 3:48 pm
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.

Posted: Tue Jul 24, 2007 3:51 pm
by devsonali
ArndW wrote:Have you set your view data options to limit to 1 row? ...
No

Posted: Tue Jul 24, 2007 3:55 pm
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.

Posted: Tue Jul 24, 2007 4:03 pm
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>?

Posted: Tue Jul 24, 2007 9:29 pm
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

Posted: Wed Jul 25, 2007 7:40 am
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> ?

Posted: Wed Jul 25, 2007 7:45 am
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 .

Posted: Wed Jul 25, 2007 9:29 am
by devsonali
Enabling the record delimiter property to DOS fixes the problem ,but I still don t understand the reason for this

Thanks

Posted: Wed Jul 25, 2007 10:10 am
by us1aslam1us
Your answer lies here:
I generated the text file in windows and trasferred it to the unix server .
[/code]