Page 1 of 1
Data Has been Truncated
Posted: Wed Jul 28, 2004 9:34 am
by appcon
Hi,
I am trying to load data into Oracle tbl. And I am getting this error saying "Data has been truncated".
I checked the size, datatype of the fields in my transformations and Oracle tbls and they match.
What else could be the problem. Did anyone come across this problem.
Any suggestion would be appreciated.
Thanks,
Sri.
Posted: Wed Jul 28, 2004 9:39 am
by chulett
HOW are you loading the data? Is this an error from Oracle or a warning from DataStage?
I'd also be curious if you have any NUMBER fields in the target table. NOTE: not NUMBER(xx) but just NUMBER.
Posted: Wed Jul 28, 2004 9:40 am
by denzilsyb
Do a TRIMB on the char/varchar fields, it could be spaces that you dont see.
How does the data look? does it look like its too long?
Posted: Wed Jul 28, 2004 9:43 am
by appcon
This msg is a warning in the datastage. When I check the data in the msg box, the data is built correctly, but is not written into the oracle tbl.
This is the msg i get.
GL_Facts..Fact_Dimension_Lkp.tgt_Fact_tbl: DSD.BCIPut call to SQLExecute returned informational message.
SQLSTATE=01004, DBMS.CODE=0
[DataStage][SQL Client]Data has been truncated
Thanks,
Srikanth.
Posted: Wed Jul 28, 2004 9:44 am
by appcon
I did use the trimB but not change in the outcome. The final data from the DS is right but still I get this msg. Also the size and types are the same.
Thanks,
Sri
Posted: Wed Jul 28, 2004 9:46 am
by appcon
Has you said I checked the oracle tbl. The datatype is just NUMBER withour any length in it.
Would it make any difference.
Posted: Wed Jul 28, 2004 10:25 am
by chulett
Yes it would, that's why I asked.
What size did you declare it in DataStage? 38? If you did, try bumping the declared size of the field in your job to 40 and the message should stop. Don't change anything else, just the size of the target field.
ps - Using ODBC? Why not use the native OCI stage?
