Yes my SOurce Table is Orcale... but it doesn't have Date...

kramaswamy (8/15/2011)

---

DBTIMESTAMP is the correct variable to pass in to a SMALLDATETIME field. See this page for more info:

http://msdn.microsoft.com/en-us/library/ms141036%28v=SQL.90%29.aspx

Check all your meta data types. Specifically, look at the meta data...

Have to do something like this.... I have a column (which holds Date) with Datatype Smalldatetime in the Destination table. Have to somehow send...

rfr.ferrari (8/15/2011)

---

according with microsoft's article http://msdn.microsoft.com/en-us/library/ms141704.aspx that show the convesions illegal/legal to differents data types of SSIS.

quillis131 (8/15/2011) It was running very sucessful, during Development.Verfied the Destination table Datatype on...

quillis131 (8/15/2011)

---

There was an error with input column "Added Date" (86) on input "OLE DB Destination Input" (47). The column status returned was: "Conversion failed because the data value overflowed...

There was an error with input column "Added Date" (86) on input "OLE DB Destination Input" (47). The column status returned was: "Conversion failed because the data value overflowed the...

I tried to cast the above expression, but it's gives me an casting error (red color) in the Data conversion Transformation....

What should I be doing for these... This is strange for me, as I colud do this package sucessfully without any kind of errors during Dev.

Never mind ... got my stuff done .... make sure you increase youe Parameter size to 1 or more in the parameter column and set the SSIS variable to Int32...

Hey ... Orcale SP should be written in a different way, the one u suggested isn't going to work. More over, if u follow my question... I was asking the...

comma(,)

Thats the problem ....made a error output flatfile after the data conversion component, but as the cloumn is not been exported from the source itself, its difficult to say. But...

Any way ...Thank you all ...atleast now I feel good as I am not the problem ...it has to be something with the Version level ..... Now hitting on other...

No luck....I tried to change that ...the same message. And I am not sure what my version is ..but can definetly say it is 2008(sql express).......This seams a bug

I cannot understand how you were able to set your PackageScope properties ...I checked, if it allows me set the property from supported to required, on another machine ...but answer...