Brian,

You are correct. We had some data from year '0200'. We are correcting the
data.

Thank you,

Sang
x6746


-----Original Message-----
From: Brian Freeman [mailto:[Email Address Removed] Friday, September 26, 2003 11:25 AM
To: sang.[Email Address Removed] LazyDBA.com Discussion
Subject: RE: Data import error importing from Oracle 8i to SQL Server
2000


Like the error says there is a date that is either too early or too late for
SQL server to accept. For Date/Time column SQL Server accepts dates from
1/1/1753 to Dec. 31, 9999. For small date/time acceptable dates are from
Jan. 1, 1900 to June 6, 2079. Check for user input error that leaves a date
outside of this range.

Good luck.
Brian Freeman

-----Original Message-----
From: sang.[Email Address Removed] [mailto:sang.[Email Address Removed] Friday, September 26, 2003 11:20 AM
To: LazyDBA.com Discussion
Subject: Data import error importing from Oracle 8i to SQL Server 2000


Hi,

I am trying to import a table from Oracle 8i database using Oracle Provider
for OLEDB and encountered the following error:

Error at Destination for Row number 38142. Errors encountered so far in
this task: 1. Insert error, column 40 ('DUE_DATE', DBTYPE_DBTIMESTAMP),
status 6: Data overflow.
Insert error, column 25 ('RCVD_DATE', DBTYPE_DBTIMESTAMP), status 6: Data
overflow.
Invalid character value for cast specification.
Invalid character value for cast specification.

The 'DUE_DATE' and 'RCVD_DATE' columns are 'datetime'.

Thanks in advance.

Thank you,

Sang

---------------------------------------------------------------------
TO REPLY TO EVERBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY
To unsubscribe, e-mail: mssqldba-[Email Address Removed] additional commands, e-mail: mssqldba-[Email Address Removed]MS Sql Server LazyDBA home page