Bad trailing quote character at field "LAST_GOODS_RECEI

[ysrini9]

Hi All,

While running the DataStage(PX) job.

We are getting below Warning message.
==========================
Bad trailing quote character at field "LAST_GOODS_RECEIVED_DATE"; looking for '34' but found ' ', at offset: 152
===========================

Could please kindly help me out cause and solution for this.

Thanks in Advance
Thanks and Regards
S R I N I

[ray.wurlod]

Describe this column more fully. What is its purported length? Is the record fixed width? Have you specified " as the quote character? Has a line in the file been truncated? 34 is ASCII for the " character; the warning message says it was looking for one of those, but found an empty string (possible a pad character 0x00 or an end of string).

[murakk]

Hi All,

While running the DataStage(PX) job.

We are getting below Warning message.
==========================
Bad trailing quote character at field "LAST_GOODS_RECEIVED_DATE"; looking for '34' but found ' ', at offset: 152
===========================

Could please kindly help me out cause and solution for this.

Thanks in Advance
Thanks and Regards
S R I N I

HI Srini,

Even i am facing the same problem...even i am gettin the same warning... few records are been rejected from the file...did u solve the problem...if so please help me out....
Thanx in advance

[ray.wurlod]

I doubt that U solved the problem. If U had solved the problem then U would have posted the solution.

The second person personal pronoun in English is spelled "you", not "u".

Please strive for a professional standard of written English on DSXchange, not least because it aids those whose first language is not English.

[blazDelParis]

Hi,
i get the same problem.
I've noticed it happens when you have a csv file as input

my csv file is ";"-field-separated, all fields are surrounded with quotes like this :

Code: Select all

"abc";"123";"";"e7r8t9"
"abd";"123";"31/01/2000 14:58:22";"e7r8t9"
"aby";"";"31/01/2000 14:58:22";"e7r8t9"

Some fields may be null, like the second and the third one in my example.
The third field is a timestamp.
i've set it as a nullable timestamp and with a format string like this :
"%dd/%mm/%yyyy %hh:%nn:%ss"

When a previous field to the timestamp field is null, it seems that datastage has some problems to parse the file.
Because when I get this error , I get in the log some info like :

Code: Select all

can't parse "";"e7r8t9" as timestamp (string format : "%dd/%mm/%yyyy %hh:%nn:%ss"  )

It seems that parsing problem comes only whith timestamp formatted fields.

I've surrounded the problem , I've set the input timeStamp field as a varchar(19) field, and then in a transformer stage, I convert it in a timestamp like that :

Code: Select all

If trf.TRANS_DATE<>"" then StringToTimeStamp(trf.TRANS_DATE, "%dd/%mm/%yyyy %hh:%nn:%ss") else SetNull()

If someone has a more elegant solution, please tell me, because I've got lots of nullable timestamp fields...

[HariK]

I've noticed it happens when you have a csv file as input
my csv file is ";"-field-separated....

Did you mean sequential file?

[blazDelParis]

Yes, I mean a sequential file