Delimiter for field "COL_NAME" not found;

[kumar_s]

What is the delimiter for your file? You have many such records. Get the n-1 or n+1 record's primary key, and look into the the database, check if you have any special character in columns of the nth records.

[ray.wurlod]

The delimiter character is "|" as stated earlier, but there is no "|" character in any of those records. This would only work if your record schema referred to one field only.

[DS_MJ]

conv_FA_001_0804_2006_4,0: Delimiter for field "AXASS" not found; input: {20 S T A M P I N G , 20 B L A N K 20 & 20 T R I M , 20 P / N 20 6 4 9 2 9 - 0 1 A , 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20}, at offset: 0

Hello Ray/kumar_s/us1aslam1us:

There are two files where the AXASS column is output to. So I go in UNIX and view the data for those two files. I do see the '|'. So in the director when you see 20 20 20 ...I dont know what that is.


I do a $ head -6160 MF_FAPAX | tail -1 on the UNIX file to view the 6159 record, I see the follwoing data for that record.

FILE 1
50983|50983| |A|001| 04-04001014| | |TEAMMATE WORKPAPER SOFTWARE-9 |19046.00|12647|0|0|1| 6/01/2004|2004|9|300|206|19046.00|3174.33|0.00|0.00|50983|11427.60|19046.00| 6/01/2004|2004|500|0.00|0.00|ACR|0.00|0|405|0|TEAMMATE WORKPAPER |50983

The last column is the AXASS column.

FILE 2
56189|STEP LOWERS C'CASE HALVES

The first column is the AXASS column.

Both the files look good, I do see a delimiter in both.

The only thing I notice is that when I extract the data from Db2 some of the columns show null values and the nullable field is set to not nullable for those columns. So I am going to set these columns in the transform target side as nullable except for the key fields. Hopefully these warning messages for these records will go away.

[ray.wurlod]

20 is hexadecimal for 32, which is the space character. I don't see pipe characters in those records, but agree that there are some in the final record that you have just posted.

See if you can find any lines in the file(s) where there is no pipe character, for example grep -v '|' filename