Page 1 of 1
Posted: Wed Oct 20, 2010 1:21 pm
by jcthornton
Is Unicode enabled on the target table?
Is Unicode setup on all intermediate links in the job(s) between the good source file and the database load?
Can you confirm (maybe with a copy stage to a sequential file or dataset) if the data being pushed to the database has retained the special characters or not?
Posted: Wed Oct 20, 2010 2:11 pm
by chowdary_kish
jcthornton wrote:Is Unicode enabled on the target table?
Is Unicode setup on all intermediate links in the job(s) between the good source file and the database load?
Can you confirm (maybe with a copy stage to a sequential file or dataset) if the data being pushed to the database has retained the special characters or not?
im not sure about the Target Table but we have Extended Unicode throughout Datastage for those fields.
One more point to make a note of is When they(DRM Team) produce a extract of the Target table into a sequential file im seeing those Speacial characters in that file.
Posted: Wed Oct 20, 2010 11:40 pm
by jcthornton
If you could check on that - I believe there are steps that the DBAs have to take to enable Unicode in the database. If they have not been done, then it doesn't matter what you do with DataStage (well almost - there are some not-worthwhile ways you can 'hide' Unicode but it would take some custome encoding and decoding efforts).
The only other thing to check is that suggestion to use a copy stage and verify that you are attempting to insert the valid Unicode characters into the database.
If the values are being sent to the database in Unicode and are coming back ASCII, then that narrows down your problem scope considerably.
If you aren't sending Unicode to the database, then you know the problem is somewhere between the DRM extract and the database.