Re: MDAC and Oracle9

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Sid Eaton (sid.eaton_at_cusys.edu)
Date: 04/09/04


Date: 9 Apr 2004 12:45:37 -0700

We are having, apparently, the same problem here. Also with Oracle
9.2.0.4.0.

We have tried Oracle's native driver, the MS OLE DB driver for Oracle
and the MS OLE DB Driver for ODBC Drivers using either the Microsoft
or Oracle ODBC drivers. We have had some success retriving data with
a linked server connection using Microsoft OLE DB Provider for ODBC
Drivers using Microsoft ODBC for Oracle {version 2.573.9030.00}. [Not
sure what MDAC provided this]

All other methods fail with error messages like:

Server: Msg 7356, Level 16, State 1, Line 2
OLE DB provider 'OraOLEDB.Oracle' supplied inconsistent metadata for a
column. Metadata information was changed at execution time.
OLE DB error trace [Non-interface error: Column 'MIN_EXTENTS'
(compile-time ordinal 12) of object '"SYS"."ALL_TABLES"' was reported
to have a DBTYPE of 130 at compile time and 5 at run time].

or

Server: Msg 7318, Level 16, State 1, Line 2
OLE DB provider 'MSDASQL' returned an invalid column definition.
OLE DB error trace [Non-interface error: OLE/DB provider returned an
invalid column definition.].

We are getting error messages like this from W2K Server SQL Server
2000 machines whether the Oracle 8i or 9i drivers are installed if the
linked target is Oracle 9.2.0.4.0.

We suspect that SQL Server 2000 is using old methods to communicate
with Oracle that are not appropriate for Oracle 9.2.0.4.0 and perhaps
other releases around that version. Since Oracle is working fine and
connections to it to retrieve data using a Windows script file are
successful [using ODBC and UDL files], my current suspicion is that a
patch will be required for MS SQL Server 2000 to work with more recent
versions of Oracle.

Anyone else having this experience or perhaps information on a fix for
this problem?



Relevant Pages

  • Re: Oracle Linked Servers
    ... To use distributed transactions with the Oracle OLE DB Provider in your ... I created a blank database in sql server ...
    (microsoft.public.sqlserver.server)
  • Incredibly slow SQL Server --> Oracle migration.
    ... SQL Server 2000 and Oracle 10g. ... the Oracle schema is the target. ... I have made sure I've got all the updated OLE DB drivers. ...
    (microsoft.public.sqlserver.dts)
  • Re: Incredibly slow SQL Server --> Oracle migration.
    ... I think it just has to do with the drivers and how they are used. ... I note that in SSIS a 3rd party has specifically written an Oracle speed loading component. ... between SQL Server 2000 and Oracle 10g. ... I have made sure I've got all the updated OLE DB drivers. ...
    (microsoft.public.sqlserver.dts)
  • RE: ODBC to Oracle 64bit missing rows
    ... the set of Oracle queries that I'm running ... through the linked server right now haven't given me that error.... ... I'm trucking on with 64-bit & Oracle's OLE DB drivers. ... I am on SQL Server 2005, ...
    (microsoft.public.sqlserver.connect)
  • Re: More question on OLE DB
    ... I have another question on opening a database using OLE DB. ... I understand that Provider=MSDAORA is Microsoft Oracle OLE DB Provider. ... Does Oracle corporation have their own Oracle OLE DB Provider? ... I haven't noticed any performance difference between the drivers. ...
    (microsoft.public.vb.general.discussion)