Unable to view the table contents

devidotcom · Post by **devidotcom** » Tue Feb 05, 2008 10:01 pm

Hi All,

I have issue where in I am using a ODBC Enterprise stage and trying to read data from the table.
We have setup the connection and trying to access the Oracle table for the first time in the DataStage.
The job runs fine but I get this following error message. Also when I view the data from the table I see question marks (?) for each column values.

APT_CombinedOperatorController,0: Invalid character conversion found converting to ISO-8859-1, substituting. [nls/converter.C:830]

The NVL_CHARACTER SET forthe database is "AL32UTF8". I guess we have issues with the character set in DataStage.

Is there a solution to this. Thanks in advance

devidotcom · Post by **devidotcom** » Tue Feb 05, 2008 10:03 pm

I have researched the site for Invalid Character conversion also. But could only get to know that the character set is not in sync with that of Oracle.

What are the environment variables APT_INPUT_CHARSET or APT_OUTPUT_CHARSET used. Can we use these here.

ray.wurlod · Post by **ray.wurlod** » Wed Feb 06, 2008 12:20 am

How is the NLS_LANG environment variable set?

devidotcom · Post by **devidotcom** » Wed Feb 06, 2008 1:02 am

How do I check that?

devidotcom · Post by **devidotcom** » Wed Feb 06, 2008 4:22 am

How do I check that?

ray.wurlod · Post by **ray.wurlod** » Wed Feb 06, 2008 4:57 am

The same way you'd check any environment variable.

Code: Select all

echo $NLS_LANG

executed from any DataStage job.

devidotcom · Post by **devidotcom** » Wed Feb 06, 2008 5:14 am

Thank you
I executed the command but it did not display anything an empty string

manishk · Post by **manishk** » Wed Feb 06, 2008 10:58 am

Guess if you make NLS as NONE then it will work

devidotcom · Post by **devidotcom** » Wed Mar 05, 2008 3:03 am

There are some patches that are been sent by IBM so I we can consider this to be workaround.

ray.wurlod · Post by **ray.wurlod** » Wed Mar 05, 2008 3:16 am

Please give more details. What are the patches, with what eCase number(s) is each associated and, most importantly, did they fix the problem?

devidotcom · Post by **devidotcom** » Wed Mar 05, 2008 3:23 am

Will keep this posted... We are yet to receive the same in a week or so. The case number was 712389