Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
sarorelasoul
Starting Member
29 Posts |
 Posted - 2008-05-05 : 15:56:52
|
| Hi,I'm importing data from and oracle database to an SQL one through a SSIS package, I'm getting this error:"The output column "earned_hours" has a precision that is not valid. The precision must be between 1 and 38".the package runs but returns this column as NULL valuesearned_hours is of type "NUMBER" in oracle (some of the values are decimals), I tried making it numeric(x,y),float or decimal(x,y), but I'm still getting the same results.does anybody know why is this happening or have a solution for this error?Thanks |
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2008-05-05 : 23:10:02
|
| Double check values in the column on Oracle, ensure them can fit in column on sql server. |
 |
|
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
Posted - 2008-05-06 : 00:08:46
|
| How have you declared the column earned_hours? |
|
|
|
sarorelasoul
Starting Member
29 Posts |
Posted - 2008-05-06 : 12:10:09
|
| rmiao:The point is the coulumn in oracle is of type NUMBER which can hold integers, floats, doubles and so on.In my case the column values are both integers and floats.oracle "Number" does not set the precision or scale which will cause SSIS to not be able to bring in data from those columns.I know the problem but I need a good fix, All the solutions I found were converting this field to varchar or not using OLEBD destination in SSIS.visakh16:yes I'm sure the column is declaredThanks |
|
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2008-05-06 : 12:15:51
|
| check this out:http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1489287&SiteID=1 |
|
|
|
sarorelasoul
Starting Member
29 Posts |
Posted - 2008-05-06 : 14:08:12
|
| Thanks sodeep, I tried setting the precision and scale and it worked |
|
|
|
|
|
|
|
|
The output column has a precision that's not valid