Special character being ignored by Oracle Stage

A forum for discussing DataStage<sup>®</sup> basics. If you're not sure where your question goes, start here.

Moderators: chulett, rschirm, roy

Post Reply
deepa_shenoy
Participant
Posts: 95
Joined: Thu Sep 24, 2009 12:15 am
Location: India

Special character being ignored by Oracle Stage

Post by deepa_shenoy »

Hi,

I have a simple ETL flow.

ODBC Stage--------> ORA Stage

The source has a special character(similar to ' ) which is read by ODBC stage but being replaced by a reverse question mark symbol in the target by the Oracle stage.

How to avoid this?

Thanks in advance.

Deepa
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Find out what the character actually is and whether it is correctly handled by the locale and map you are using for DataStage, then make sure that the NLS_LANG setting for Oracle is compatible.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Aquilis
Participant
Posts: 204
Joined: Thu Apr 05, 2007 4:54 am
Location: Bangalore
Contact:

Post by Aquilis »

1. For Oracle Enterprise Stage, datatype in DS for the column should be 'NVarchar'.
2. For DRS stage, varchar is ok.
3. Better to keep NLS_MAP & NLS_Language as 'UTF-8 ' in both DS & Oracle respectively.
Aquilis
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Don't know how you can suggest that without knowing the characterset of the target Oracle database. :?
-craig

"You can never have too many knives" -- Logan Nine Fingers
asorrell
Posts: 1707
Joined: Fri Apr 04, 2003 2:00 pm
Location: Colleyville, Texas

Post by asorrell »

Craig's answer is correct - you must set the character set correctly for BOTH the incoming data and the outgoing data. It is highly doubtful that you can change the Oracle map to UTF8 if that isn't the default, the "ripple effect" of changing the map could be significant. In the US we get spoiled because the default of UTF8 works for the basic US characters.

Please note, that setting both correctly does not insure that the character will be mapped. It may be a case where the character in the source map does not have an equivalent character in the target map. In those cases you'll need to either live with the "?" or manually parse the incoming field and replace the offending characters (something I've had to do at several sites).
Andy Sorrell
Certified DataStage Consultant
IBM Analytics Champion 2009 - 2020
Post Reply