SQL Server Migration Assistant - Data Conversion Errors

Author

Data Conversion Errors

Michael Thorne

2005-09-28, 11:24 am

I am attempting to convert an Oracle 8.0.5 database to SQL Server 2000.
I have been able to successfully convert the database structure using
SSMA, but I am receiving errors when copying the data. Depending on the
provider used, I receive the following errors:

Oracle Provider for OLE DB:
JDBC Error: [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]Could
not execute query against OLE DB provider 'OraOLEDB.Oracle'.

Microsoft OLE DB Provider for Oracle:
JDBC Error: [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]OLE DB
provider 'MSDAORA' reported an error.

Any help with this issue is greatly appreciated.

- Mike

Michael Thorne

2005-09-30, 11:24 am

I was able to work around this by using the Beta of version 2.0 of SSMA.
For those with my same issue, the link to the download can be found
here:
http://www.microsoft.com/downloads/...&DisplayLang=en

Now I have an issue where a table row in Oracle is larger than the
maximum for SQL Server. Is there any way around this?

Mike

Michael Thorne wrote:
> I am attempting to convert an Oracle 8.0.5 database to SQL Server 2000.
> I have been able to successfully convert the database structure using
> SSMA, but I am receiving errors when copying the data. Depending on the
> provider used, I receive the following errors:
>
> Oracle Provider for OLE DB:
> JDBC Error: [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]Could
> not execute query against OLE DB provider 'OraOLEDB.Oracle'.
>
> Microsoft OLE DB Provider for Oracle:
> JDBC Error: [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]OLE DB
> provider 'MSDAORA' reported an error.
>
> Any help with this issue is greatly appreciated.
>
> - Mike

Joe Yong

2005-09-30, 11:24 am

Depends. Is the data stored really taking up more than 8060bytes per row or
have the columns just been declared bigger than 8060 byte (but no rows
actually exceed that)?

The former is fairly easy to deal with since it's just tweaking the column
definitions. If it does exceed 8060 bytes, you may have to get a bit more
creative (eg. views, redesign table, etc...)

joe.

"Michael Thorne" <Michael.Thorne@nospam.us.abb.com> wrote in message
news:%23qZDzRdxFHA.3040@TK2MSFTNGP10.phx.gbl...[color=darkred]
>I was able to work around this by using the Beta of version 2.0 of SSMA.
>For those with my same issue, the link to the download can be found here:
> http://www.microsoft.com/downloads/...&DisplayLang=en
>
> Now I have an issue where a table row in Oracle is larger than the maximum
> for SQL Server. Is there any way around this?
>
> Mike
>
>
> Michael Thorne wrote:

Dandy Weyn [Dandyman]

2005-10-01, 8:24 pm

You can do a 'manual' conversion on this one to resolve the issue.
Kinda break the tables appart into 2 tables, create a view on it.

Also ..SQL 2005 will let you get around the max rowsize limit

--
Dandy Weyn
[MCSE-MCSA-MCDBA-MCDST-MCT]
http://www.dandyman.net

Check my SQL Server Resource Pages at http://www.dandyman.net/sql
"Michael Thorne" <Michael.Thorne@nospam.us.abb.com> wrote in message
news:%23qZDzRdxFHA.3040@TK2MSFTNGP10.phx.gbl...[color=darkred]
>I was able to work around this by using the Beta of version 2.0 of SSMA.
>For those with my same issue, the link to the download can be found here:
> http://www.microsoft.com/downloads/...&DisplayLang=en
>
> Now I have an issue where a table row in Oracle is larger than the maximum
> for SQL Server. Is there any way around this?
>
> Mike
>
>
> Michael Thorne wrote:

Sponsored Links