|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
Search found 4 matches |
Author |
Message |
Topic: Issue in parsing characters such as °, ³ (superscript) |
Avocado's number
Replies: 10 Views: 5926
|
Forum: WebSphere Message Broker (ACE) Support Posted: Mon Apr 15, 2013 3:58 am Subject: Issue in parsing characters such as °, ³ (superscript) |
The text encoding for the input file is UTF-8. However, the text encoding for this particular field was set to <dynamically set>. I changed this to UTF-8 and I am able to receive a correct repre ... |
Topic: Issue in parsing characters such as °, ³ (superscript) |
Avocado's number
Replies: 10 Views: 5926
|
Forum: WebSphere Message Broker (ACE) Support Posted: Mon Apr 15, 2013 1:34 am Subject: Issue in parsing characters such as °, ³ (superscript) |
I dropped and re-created the database to change the codepage, then created the tables and tried the insert via my flow.
Here is a summary of what I have tried so far-
1. Parsed the input file cor ... |
Topic: Issue in parsing characters such as °, ³ (superscript) |
Avocado's number
Replies: 10 Views: 5926
|
Forum: WebSphere Message Broker (ACE) Support Posted: Sun Apr 14, 2013 10:25 pm Subject: Issue in parsing characters such as °, ³ (superscript) |
The database was using a code page of 1252. This has been changed to 1208 and now the representation of °C has become ┬░C. Also, the data type of the column in DB2 is CHARACTER. Any point ... |
Topic: Issue in parsing characters such as °, ³ (superscript) |
Avocado's number
Replies: 10 Views: 5926
|
Forum: WebSphere Message Broker (ACE) Support Posted: Fri Apr 12, 2013 4:00 am Subject: Issue in parsing characters such as °, ³ (superscript) |
I am using a CSV file as an input to a FileInput node in my flow. The records present in the file are inserted into the database (DB2 9.7).
One of the records present in the CSV carries an entry ° ... |
|
|
|