unable to view data in sequential file

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
raji33
Premium Member
Premium Member
Posts: 151
Joined: Thu Sep 23, 2010 9:21 pm
Location: NJ

unable to view data in sequential file

Post by raji33 »

Hi All,

Iam trying to view data in sequential file but it is throwing the following error, can any one please help me. Thanks!

I IIS-DSEE-TFSC-00001 10:13:51(011) <main_program> APT configuration file: /opt/IBM/InformationServer/Server/Configurations/default.apt
##W IIS-DSEE-TFIG-00182 10:13:52(000) <Sequential_File_20,0> Bad trailing quote character at field "TIMESTMP"; looking for '34' but found '.', at offset: 261
##W IIS-DSEE-TOIX-00154 10:13:52(001) <Sequential_File_20,0> Import warning at record 0.
##W IIS-DSEE-TOIX-00018 10:13:52(002) <Sequential_File_20,0> Import unsuccessful at record 0.
##W IIS-DSEE-TFIG-00182 10:13:52(003) <Sequential_File_20,0> Bad trailing quote character at field "TIMESTMP"; looking for '34' but found '.', at offset: 249
##W IIS-DSEE-TOIX-00154 10:13:52(004) <Sequential_File_20,0> Import warning at record 1.
##W IIS-DSEE-TOIX-00018 10:13:52(005) <Sequential_File_20,0> Import unsuccessful at record 1.
##W IIS-DSEE-TFIG-00182 10:13:52(006) <Sequential_File_20,0> Bad trailing quote character at field "TIMESTMP"; looking for '34' but found '.', at offset: 212
##W IIS-DSEE-TOIX-00154 10:13:52(007) <Sequential_File_20,0> Import warning at record 2.
##W IIS-DSEE-TOIX-00018 10:13:52(008) <Sequential_File_20,0> Import unsuccessful at record 2.
GJ_Stage
Participant
Posts: 131
Joined: Mon Oct 27, 2008 6:59 am

Post by GJ_Stage »

Is it fixed length file or delimiter file?
raji33
Premium Member
Premium Member
Posts: 151
Joined: Thu Sep 23, 2010 9:21 pm
Location: NJ

Post by raji33 »

its a comma seperated file
GJ_Stage
Participant
Posts: 131
Joined: Mon Oct 27, 2008 6:59 am

Post by GJ_Stage »

Please check your sequencial file in unix using below command
awk -F ',' '{print $34}' infile | sort -n | uniq -c
It might be your data contains some wrong value.
raji33
Premium Member
Premium Member
Posts: 151
Joined: Thu Sep 23, 2010 9:21 pm
Location: NJ

Post by raji33 »

command not found . we are using linux operating system(bash)
GJ_Stage
Participant
Posts: 131
Joined: Mon Oct 27, 2008 6:59 am

Post by GJ_Stage »

Ok. I send command for Unix.. Might be Number of fields are less comparing with your file.
jwiles
Premium Member
Premium Member
Posts: 1274
Joined: Sun Nov 14, 2004 8:50 pm
Contact:

Post by jwiles »

The error message says a lot:
Bad trailing quote character at field "TIMESTMP"; looking for '34' but found '.', at offset: 261
What is your schema for the file and what do the records actually look like?

Regards,
- james wiles


All generalizations are false, including this one - Mark Twain.
raji33
Premium Member
Premium Member
Posts: 151
Joined: Thu Sep 23, 2010 9:21 pm
Location: NJ

Post by raji33 »

actually i have took the target table metadata table definitions so i dont think there is a problem of fields being less in file. and schema of file is table structure
jwiles
Premium Member
Premium Member
Posts: 1274
Joined: Sun Nov 14, 2004 8:50 pm
Contact:

Post by jwiles »

That may be so, but you failed to supply the answer to my questions:

What is the schema being used to read the file? Post the actual schema, don't just tell me where you got it from.

What do the records which failed look like? Post the records themselves--copy and paste from vi, more, less, head, tail, whatever

The point being: The schema being used to read the file does not match the file's data in some way.
- james wiles


All generalizations are false, including this one - Mark Twain.
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

I expect that this is a non-default timestamp format, which you should be able to resolve by providing the correct timestamp format in the metadata (whether that's in the job or in a schema file). The import operator is looking for the trailing quote character or a timestamp character, but found "." character.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Post Reply