Suppressing NLS warnings

[snassimr]

Hi , everybody !!!

I have a question regarding NLS .

I have a job that each run have about NLS 2000 warnings since DS failed to map some values are come from Database. My job fails after 50 warnings . I increase it to 2500 in Director but each time the job is run by job sequence and the job failed after 50 warnings.

1. If any way to supress NLS warning not counting them ?
2. How to increase the number of allowed warnings in case the job run with Job Sequence ?

Thanks

[ray.wurlod]

As with any metadata mismatch warning, the only way to suppress them is to "get it right" - specify mapping the correctly handles all of the characters in your source data. In extreme cases, build a map (or hire an expert to do so).

[chulett]

ps. "I increase it to 2500 in Director" just means you have changed the default value for you on your PC when you manually launch the job from the Director. Now, if you run the Sequence job with that warning higher level, it is supposed to pass it down to all Job Activity stages automatically. Are you not seeing that?

pps. You still need to get things fixed and mapped correctly rather than "cheat" and allow for the warnings. The above is to help answer question #2 and not to circumvent your need to do things right.

[asorrell]

If the target database supports the NLS characters in its default map, you can set mapping to "NONE" in your server job to route them through from source to target without letting DataStage try to figure them out and map them to UTF8.

Please note - check this out carefully in your target table to insure it transferred the characters correctly.

Do not use this if you are using multiple data sources with different language maps, as it will cause problems with joins, etc.

Note: I agree with Craig - the best method is to figure out how mapping works and get the maps set correctly to insure you get appropriate results...