| Author |
Message |
prasad111

Group memberships: Premium Members
Joined: 19 May 2006
Posts: 142
Points: 1672
|
|
| DataStage® Release: 8x |
| Job Type: Parallel |
| OS: Unix |
|
Job Design
| Code: |
| DatasetStage--> Copy --> InvestigateStage--> Peek |
Warning
| Code: |
| CopyToAll: When checking operator: When binding output schema variable "outRec": When binding output interface field "NameDomain_USPREP" to field "NameDomain_USPREP": Implicit conversion from source type "ustring[max=100]" to result type "string[max=100]": Possible truncation of variable length ustring when converting to string using codepage UTF-8. |
In Investigate stage uses Character Concatenate Investigate option, whenever this investigation option is selected we see the above error. As there is no option to set NULL VALUE=" " how to eliminate this warning apart from supression using message handler?
Thanks for all your replies
Prasad
|
|
|
|
|
 |
ray.wurlod
Participant
Group memberships: Premium Members, Inner Circle, Australia Usergroup, Server to Parallel Transition Group
Joined: 23 Oct 2002
Posts: 41029
Location: Canberra, Australia
Points: 228711
|
|
|
|
|
|
|
Your use of the extended property Unicode is inconsistent across the stage. A ustring[max=100] is a VarChar(100) with Unicode set, a string[max=100] is a VarChar(100) with Unicode not set. Find this ...
|
_________________ Zenith Solutions (Australia) Pty Ltd
-- from obscurity to
clarity
|
|
|
|
 |
prasad111

Group memberships: Premium Members
Joined: 19 May 2006
Posts: 142
Points: 1672
|
|
|
|
|
|
Yes I have given all the columns SqlType as Varchar and Extended Unicode, still I am getting the error.
The error occurs only when used
Character Concatenate investigate type
, for the same column (no change in the job or column name, ....) when
Character Discrete Investigate type
is selected the job runs fine without warning.
|
|
|
|
|
 |
ray.wurlod
Participant
Group memberships: Premium Members, Inner Circle, Australia Usergroup, Server to Parallel Transition Group
Joined: 23 Oct 2002
Posts: 41029
Location: Canberra, Australia
Points: 228711
|
|
|
|
|
|
|
Are you able to remove Unicode from all the fields you are mentioning in the concatenation as a test? It may be that the internal result of concatenation is the "field" that is at fault here.
|
_________________ Zenith Solutions (Australia) Pty Ltd
-- from obscurity to
clarity
|
|
|
|
 |
prasad111

Group memberships: Premium Members
Joined: 19 May 2006
Posts: 142
Points: 1672
|
|
|
|
|
|
|
With or Without Unicode, I get the same warning
|
|
|
|
|
 |
ray.wurlod
Participant
Group memberships: Premium Members, Inner Circle, Australia Usergroup, Server to Parallel Transition Group
Joined: 23 Oct 2002
Posts: 41029
Location: Canberra, Australia
Points: 228711
|
|
|
|
|
|
|
OK, use a message handler to demote the warning to informational. This is a message that is unlikely to impact your processing of data.
|
_________________ Zenith Solutions (Australia) Pty Ltd
-- from obscurity to
clarity
|
|
|
|
 |
prasad111

Group memberships: Premium Members
Joined: 19 May 2006
Posts: 142
Points: 1672
|
|
|
|
 |
|
|