Warning: Data has been truncated

Post questions here relative to DataStage Server Edition for such areas as Server job design, DS Basic, Routines, Job Sequences, etc.

Moderators: chulett, rschirm, roy

Post Reply
kamal2
Participant
Posts: 2
Joined: Mon Dec 01, 2014 5:42 pm

Warning: Data has been truncated

Post by kamal2 »

Hello,

I have a warning in my Job. Warning: Data has been truncated.

The job extracts data from Oracle and loads it into SQL Server. When I extract the data I convert it from ms12 to UTF8 because I have a problem with specific characters?

The NLS in DataStage is MS1252 and in Oracle AL32UTF8 and UTF8 in SQL Server

I have change the metadata (length) of field but the problem persists


:shock:
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Can you post the actual unedited error message, please?
-craig

"You can never have too many knives" -- Logan Nine Fingers
kamal2
Participant
Posts: 2
Joined: Mon Dec 01, 2014 5:42 pm

Post by kamal2 »

The message is :

WARNING: JOB_NAME.TRANSFORMER_NAME: DSD.BCIPut call to function SQLExecute returned informational message.
SQLSTATE=01004, DBMS.CODE=0
[DataStage][SQL Client]Data has been truncated

COL1 = "N"
COL2 = "1-LWSZXT"
COL3 = "S41"
COL4 = "Seguridad CONTRA"
COL5 = 2010-03-01 04:08:34
priyadarshikunal
Premium Member
Premium Member
Posts: 1735
Joined: Thu Mar 01, 2007 5:44 am
Location: Troy, MI

Post by priyadarshikunal »

any other warning or just this one?

Anyways, try to find if there is any difference between the table structure defined in the job and in database.

If its UTF8 in source and target, any particular reasons for not using the same character set on datastage?

It doesn't look like that in the data you posted but do you have any multi-byte/accented/special character in your source data causing overflow in bytes assigned?
Priyadarshi Kunal

Genius may have its limitations, but stupidity is not thus handicapped. :wink:
roy
Participant
Posts: 2598
Joined: Wed Jul 30, 2003 2:05 am
Location: Israel

Post by roy »

Hi,
Try to check actual column lengths.
sometimes even the wrong size in ds compared with DB can cause this.
if you had any special cars the you wouls have ot NLS warning since ms1252 does't support them.
IHTH,
Roy R.
Time is money but when you don't have money time is all you can afford.

Search before posting:)

Join the DataStagers team effort at:
http://www.worldcommunitygrid.org
Image
Post Reply