sequencer failing due to warnings

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
pradeep_nov18
Participant
Posts: 92
Joined: Wed Mar 05, 2008 4:09 am
Location: chennai
Contact:

sequencer failing due to warnings

Post by pradeep_nov18 »

Hi Experts,

How to resolve this warning since it is generating for each record:

APT_CombinedOperatorController(0),0: Invalid character(s) ([xFF0C]) found converting Unicode string (code point(s): Manual payment #5100001146[xFF0C]61 ) to codepage ISO-8859-1, substituting.

Is this warning is due to this impact: I am using NLS-Map = UTF-16 in source stage and project_default in the Job level and project_default in the target(teradata).my source is sap data

and please let me know how to eliminate this warning
pradeep.v
Nripendra Chand
Premium Member
Premium Member
Posts: 196
Joined: Tue Nov 23, 2004 11:50 pm
Location: Sydney (Australia)

Post by Nripendra Chand »

is your target database Teradata. just check the DDL of teradata table to see if columns are Unicode enabled.
-Nripendra Chand
Nripendra Chand
Premium Member
Premium Member
Posts: 196
Joined: Tue Nov 23, 2004 11:50 pm
Location: Sydney (Australia)

Post by Nripendra Chand »

Also which stage you are using to load records into Teradata?
-Nripendra Chand
pradeep_nov18
Participant
Posts: 92
Joined: Wed Mar 05, 2008 4:09 am
Location: chennai
Contact:

Post by pradeep_nov18 »

Thanks for the reply.

I am Using Multiload stage with Tpump has a option.
pradeep.v
pradeep_nov18
Participant
Posts: 92
Joined: Wed Mar 05, 2008 4:09 am
Location: chennai
Contact:

Post by pradeep_nov18 »

Nripendra Chand wrote:Also which stage you are using to load records into Teradata?
Unicode is disabled
pradeep.v
toshea
Participant
Posts: 79
Joined: Thu Aug 14, 2008 6:46 pm

Post by toshea »

Sounds like your source stage is using an NLS map of UTF-16, but your target stage is using a project default of ISO-8859-1. Your source stage is emitting a xFF0C character which apparently has no represenation in ISO-8859-1. Try setting the job NLS map to UTF-8, and set the Client character set in the Teradata stage to UTF8.
Post Reply