Column data 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
meena
Participant
Posts: 430
Joined: Tue Sep 13, 2005 12:17 pm

Column data truncated

Post by meena »

Hi All,
Good Morning,
I am getting this warning :

Code: Select all

Pyhth..Map_re_grt: The column data has been truncated to 'R'.
Pyhth..Map_re_grt: The column data has been truncated to 'S'.

Actually I am invloved in redesinging of this job. I am not sure for what reason I am getting this warning.

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

Post by chulett »

Typically because you've defined your metadata as having a size of 1.
-craig

"You can never have too many knives" -- Logan Nine Fingers
rwierdsm
Premium Member
Premium Member
Posts: 209
Joined: Fri Jan 09, 2004 1:14 pm
Location: Toronto, Canada
Contact:

Re: Column data truncated

Post by rwierdsm »

Hi Meena,

Typically, DataStage doesn't care about the data contents until you try to insert into a Database table or some other place where data is strongly 'typed'. Usually I get this error when I've been carrying data that is defined with greater length than the target database.

Check the metadata for your target table column (or whatever is hosting your target data) and ensure it lines up with the metadata in the DS stage that is passing the data to the target.

Hope this helps,

Rob
Rob Wierdsma
Toronto, Canada
bartonbishop.com
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

You are correct in that it is 'enforced' when transferring to a passive stage like an RDBMS stage.

In my experience, the warnings noted in the original post are generated by DataStage because the size declared in the job is smaller than the actual data. DataStage then truncates the data so as to not upset the database.

If the field size is smaller in the actual target field than declared in the job, you would see the data actually being rejected and an rdbms error generated. Now, granted, all this is from working with Oracle... perhaps other databases truncate oversized data - Oracle rejects it.
-craig

"You can never have too many knives" -- Logan Nine Fingers
meena
Participant
Posts: 430
Joined: Tue Sep 13, 2005 12:17 pm

Post by meena »

Thank you..
I came out of the warnings. It was the problem with length of metadata.
Post Reply