Can you try to load this data into a flat file first and convert the special characters/junk characters into readable format. In unix you should be able to use AWK to do this. If you need those special characters just as they are in the source, then sorry! this solution might not be of help to you.
Hi Charita ,
Thanks for the answer
but the problem is if i manualy insert those character in using insert statement than they are visible in oracle. Oracle is supporting those charcter and displaying them . So they are readable in UTF8 encoding.
Can any1 explain why INFA is not supporting these characetr
1 of 1 people found this helpful
So, oracle, as other database management systems, do conversion between oracle client code page and oracle server code page.
PowerCenter communicates with oracle server through oracle client by target,source definition. In the PowerCenter source/target definition you can or even must specify code page of oracle client. The conversion UTF-8 - AL32UTF is done by oracle client and server interface. So set informatica target and oracle client to UTF-8.
As far oracle National Language Support is concerned see link below:
I presume the code page for Integration Service and Source definition in Workflow Manager is set properly.
I you are not sure try to read data from your flat file and input them to flat file with source code page set in Workflow Manager to UTF-8.
Check if your target flat file is correct in terms of you dissepearing characters. If your characters does not exists in the target, you have problem before ORACLE.
Hi Cezary ,
Thanks i will try this out and let you knw.
But i have 1 ques AL32UTF8 is a super set of UTF8. So we should have encoding for DB and informatica should be same or the encoding for informatica can be super set for the DB ? I am not getting why informatica is behaiving in this way.
Thanks for the questions.
The ORACLE UTF8 and UTF-8 is different code page. See please following URL:
AL32UTF8 is equivalent of UTF-8 but not oracle UTF8. Oracle uses confusing names for code pages.
The special characters which you have mentioned (â/Â) can be read by using the following steps.
1)Open the flat file source definition in Source Analyzer in informatica.
2)In 'Table' tab Click 'Advanced' (Present in right corner bottom)
3)In File Format-> Code Page-> MS Windows Latin 1(ANSI), superset of Latin 1. (Set the Code Page as mentioned)
Please let me know if it is working fine or still there is some concern.
Hi Rajan ,
Thanks for the reply i am using MS Windows Latin 1(ANSI), superset of Latin 1 now and its working fine.
I have the same issue. Please help me!!!!
I set the input file to MS windows latin1. I can see the french character in preview data. I turned on verbose data and see the french characters just fine. But as soon as i loaded to the target table (oracle), everything became junk like what you said '?' or upside down '?'. May i ask what is your nls language, territory and characterset of your database? How about your informatica server (unix box) locale?
My Informatica Server have every thingh SET to utf-8 encoding of unicode
I was facing this problem becuase of the ODBC connection used to load the DB have Code page set to MS Latin 1 i changed it to UTF -8 encoding of Unicode and the data was loading fine.
you can check this property
Workflow Manager --> Connections --> Relations --> Edit -->Code Page