Post reply

Invalid character value for cast specification

  • July 7, 2005 at 11:01 am

    #363102

    Hello All,

    I'm having a little trouble with importing an oracle table into sql server 2000 using an ODBC connection.

    The importing works okay excpet an error appears:

    Inser Error, column 228 ('TR_AUTHENT_DT', DBTYPE_DBTIMESTAMP),staus 6: Data overflow.

    Invalid character value for cast specification.

    Any help is appreciated.

    Thanks,

    Ryan

     

  • July 7, 2005 at 11:05 am

    #571977

    Do you have values before 1900/01/01?

  • July 7, 2005 at 11:13 am

    #571979

    No...I don't think the values are before that date format. I've checked the original table also...but everything okay!! weird.

    Ryan

     

  • July 7, 2005 at 11:25 am

    #571982

    What are the min a max values??

    datetime

    between 1753/01/01 and 9999/12/31

    smalldatetime

    between 1900/01/01 and 2079/06/06

  • July 8, 2005 at 8:32 am

    #572375

    Remi,

    From looking at the design of the table, the min a max value is

    datetime: betwen 1753/01/01 and 9999/12/31.

    Thanks

  • July 8, 2005 at 8:34 am

    #572377

    Now I meant in the oracle table you wanted to transer .

  • July 8, 2005 at 8:46 am

    #572389

    I may have to check with one of the DBAs since I'm not able to review the design from my local station.

     

  • July 8, 2005 at 8:48 am

    #572391

    This is the only possible explanation I can give... some dates are just wrong (not likely as I assume Oracle validates the data), or out of range.

  • July 13, 2005 at 2:09 pm

    #574115

    Remi,

    Thanks for your help!!

    Ryan

  • July 13, 2005 at 2:12 pm

    #574117

    So what was the problem?

  • July 13, 2005 at 2:25 pm

    #574125

    One possibility is that there is a column that has all date fields with format mmddyyyy and every data is entered as (1/1/1900).  I may ask the DBA to delete this column.

     

    Ryan

  • July 13, 2005 at 2:28 pm

    #574129

    You can always try to rebuild the data into the iso standard using string functions and retry the import.

Viewing 12 posts - 1 through 11 (of 11 total)

You must be logged in to reply to this topic. Login to reply