Invalid character conversion warning

srilaxmi · Post by **srilaxmi** » Tue Mar 30, 2010 12:10 am

Hi,

We are getting below warning in the datastage parallel job

Job is having one ODBC stage(gets data from SQL server) and a tranformer(does stringtodate of a job parameter) and a Oracle enterprise stage to truncate and load records into a oracle table.

Code: Select all

APT_CombinedOperatorController,0: Invalid character conversion found converting to ibm-1051, substituting.

I have removed the Stringtodate conversion and tried executing the job, but still iam getting the warning.

Let me know the possible solution for this.

Thanks in advance
Sri

gssr · Post by **gssr** » Tue Mar 30, 2010 1:06 am

Set $APT_DISABLE_COMBINATION to 'True'and try to run the job.

ArndW · Post by **ArndW** » Tue Mar 30, 2010 1:24 am

You have a character in your data which is not mappable in the IBM-1051 character set.

srilaxmi · Post by **srilaxmi** » Tue Mar 30, 2010 1:25 am

Hi Gssr,

I Set $APT_DISABLE_COMBINATION to 'True' and re-run the job but still getting the same error

sri

ArndW · Post by **ArndW** » Tue Mar 30, 2010 1:34 am

Disabling combination will tell you in which stage you are getting the error, but in this case it will be output enterprise stage.

srilaxmi · Post by **srilaxmi** » Tue Mar 30, 2010 1:53 am

Hi ArndW,

How can we overcome this issue?
Removing the non-mappable characters of IBM-1051 character set from the source data, is the only solution? or can we deal this in datastage job?

Thanks,
Sri

srilaxmi · Post by **srilaxmi** » Tue Mar 30, 2010 10:48 pm

Hi All,

Is there is any way not to get this warning? I mean can we do some conversion on the columns having special characters? if yes, how can we do that?

Thanks
Sri

ray.wurlod · Post by **ray.wurlod** » Tue Mar 30, 2010 11:23 pm

Try to discover which character(s) can not be mapped (is it into or out of?) the IBM-1051 character set.

ArndW · Post by **ArndW** » Wed Mar 31, 2010 2:22 am

If you correctly define your character sets in source and target then you won't get conversion errors. Odds are you have incorrectly declared your NLS settings in the SQL server source stage.

srilaxmi · Post by **srilaxmi** » Tue Apr 13, 2010 7:48 am

The NLS setting in SQL server stage and Oracle stage is same - Project default(ISO-8859-1)

And i dont see any NLS option "ibm-1051" in any of the stages.

If both the NLS settings are same why I am getting this warning?

Any possible solution to avoid these warnings?

(Sorry for the late post

)

Thanks

ArndW · Post by **ArndW** » Tue Apr 13, 2010 7:50 am

What are your UNIX runtime settings for NLS_LANG (check your director output for the value)?

srilaxmi · Post by **srilaxmi** » Thu Apr 15, 2010 4:19 am

I checked in Director log the value is

Code: Select all

NLS_LANG=american_america.WE8ISO8859P1

Thanks