We are reading txt files using sequential stage with Quote property set as 'double'.
But we are getting few rejections for data records like :
7724,"4957","""VENTILATION"" PNEUMONITIS",132,"Lung disease due to external agents",,"","Diagnosis","","".
Here rejects is occurring when there are double quotes used as data, ie "VENTILATION" PNEUMONITIS. To get the data loaded like "VENTILATION" PNEUMONITIS, the data file needs to include extra double quotes, """VENTILATION"" PNEUMONITIS". The first and last " are used to enclose the data field. the 2nd and 3rd is provided to so that the double quote is read as data not as enclose code. The same case for 4th and 5th double quote.
Please help.
Thanks
Abhik.
sequential stage read issue with double quotes used as data
Moderators: chulett, rschirm, roy
this record is getting rejected while being read from the sequential file stage itself.In view data we are not able to see this record.Let me tell u also this a comma delimited file and double quote has been selected for string datatype read.vamsi.4a6 wrote:May i know what is the data it is showing when i select view data in Datastage for sequential file stage for field value-"VENTILATION" PNEUMONITIS
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
This is not something that the parallel Sequential File stage does well.
Read the entire line as a single VarChar field, then use a Transformer stage both to parse and to handle the double quote characters appropriately.
This is a task that can much more easily be handled by a server Sequential File stage.
Read the entire line as a single VarChar field, then use a Transformer stage both to parse and to handle the double quote characters appropriately.
This is a task that can much more easily be handled by a server Sequential File stage.
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.