OLEDB Provider adds spaces

Hi,
as the this small prodedure demonstrates, the Oracle OLEDB Provider attaches some blanks to the constant read by the Sql-statement.
On the  opposite the Microsoft Provider MSDAORA does what normally would be expected, it only prints out 1 single character.
What is the problem, is there something to configure ?  The blankadding behaviour causes unnecessary problems.
The Oracle OLEDB Provider seems to have some problem with blanks, sometimes it adds some, sometimes it removes some.
Thanx.
Best regards
Dirk
Output Oracle provider ( with the crazy blanks following the F ) :
Used Provider OraOLEDB.Oracle.1
AttributeName : MARKER Value : -F                               -            
AttributeName : TRIMMED_MARKER Value : -F-
Output using the Microsft Provider :
Used Provider : MSDAORA.1
AttributeName : MARKER Value : -F-
AttributeName : TRIMMED_MARKER Value : -F-
Demo Procedure :
Sub Show_Blank_Problem()
Dim rs             As ADODB.Recordset
Dim strSQL     As String
Dim i              As Integer
Dim ConnectString  As String
    ConnectString = "Provider=MSDAORA; Data Source=MyOraDB;"
    ' ConnectString = "Provider=OraOLEDB.Oracle.1;Persist Security Info=False;Data Source=MyOraDB;Extended Properties="""" "
    Set OraConnect = New ADODB.Connection
    OraConnect.Open ConnectString, "scott", "tiger"
    strSQL = " select 'F' as Marker, Trim( 'F' ) as Trimmed_Marker from Dual "
    Set rs = New ADODB.Recordset
    rs.CursorLocation = adUseClient
    rs.Open strSQL, OraConnect, adOpenStatic, adLockReadOnly
    If rs.BOF And rs.EOF Then
        Debug.Print "No Data Found!"
        rs.Close
        Exit Sub
    End If
    Debug.Print "Used Provider : " & OraConnect.Provider
    Do While Not rs.EOF
        For i = 0 To (rs.Fields.Count - 1)
            Debug.Print "AttributeName : " & CStr(rs.Fields(i).Name) & " Value : " & "-" & rs.Fields(i) & "-"
        Next i
       rs.MoveNext
    Loop
    rs.Close
End Sub

To use 32 bit oraoledb, you'll need to set IIS to run in 32 bit mode.
Or, install 64 bit oledb/client instead.
Hope it helps,
Greg

Similar Messages

  • My HD is almost full. I need to add space. Can I use an external HD to continue using my startup disc as it is?

    My HD is almost full. I need to add space. Can I use an external HD to continue using my startup disc as it is?
    I create music and have run out of space. the message says 'your startup disc is almost full', and i just thought maybe buying an external hard drive and using it as the startup disc or whatever would do the trick. Does anyone know? Thanks!

    External hard drives are relatively inexpensive...see some of those on OWC, www.macsales.com
    You can use a large external drive to provide additional space by simply saving material to that volume instead of the startup disk.  You can also partition the external drive to use part for Time Machine backups, and another partition for extended space.  Or a third partition for a clone of the boot system made by Carbon Copy Cloner or SuperDuper, both free downloads, so should the internal drive have problems you could always boot from the external partition.
    All of that can be done from Disk Utility.
    Keep in mind that Mac OS X gets very unhappy when there is less than 15% of the startup disk space free.

  • BUG With 10g OleDB Provider!

    Hi there!
    I originally thought I was going mad, but now I think there's a bug in the 10g Oracle OleDB Provider. I can repeat this at will on my systems:
    * Windows XP SP2 (with all the latest Windows Update Patches)
    * Oracle Client (including OleDB Provider) v10.2.0.1.0
    * MDAC 2.8 SP1 (with Windows XP SP2)
    or
    * Windows 2000 Workstation (with all the latest Windows Update Patches)
    * Oracle Client (including OleDB Provider) v10.2.0.1.0
    * MDAC 2.7
    Here's all I have to do!
    1) Create a table with some data in Oracle (have tested this against 8i, 9i and 10g databases):
    CONN your_username/your_password@your_tns_service_name
    CREATE TABLE OLEDB_TEST
         RECORD_ID     NUMBER(5) NOT NULL,
         RECORD_DESC     VARCHAR2(50) NOT NULL
    INSERT INTO OLEDB_TEST VALUES(0    , '0     is OK!');
    INSERT INTO OLEDB_TEST VALUES(1    , '1     is OK!');
    INSERT INTO OLEDB_TEST VALUES(10   , '10    is wrong - comes out as 0');
    INSERT INTO OLEDB_TEST VALUES(12   , '12    is OK');
    INSERT INTO OLEDB_TEST VALUES(100  , '100   is wrong - comes out as 0');
    INSERT INTO OLEDB_TEST VALUES(120  , '120   is wrong - comes out as 20');
    INSERT INTO OLEDB_TEST VALUES(1200 , '1200  is wrong - comes out as 0');
    INSERT INTO OLEDB_TEST VALUES(1230 , '1230  is wrong - comes out as 230');
    INSERT INTO OLEDB_TEST VALUES(12300, '12300 is wrong - comes out as 300');
    INSERT INTO OLEDB_TEST VALUES(12340, '12340 is wrong - comes out as 2340');
    COMMIT;2) Run some VBScript (which you can do in VB6, ASP or however else you want to add it in):
    ' Constants for the connection string
    Const strUSER = "your_username"                    ' e.g. SCOTT
    Const strPASSWORD = "your_password"               ' e.g. TIGER
    Const strTNS_SERVICE_NAME = "your_tns_service_name"     ' e.g. ORCL
    Dim objConnection
    Dim objRecordset
        ' make sure we have a temp directory to write to, and that any existing file is deleted
        On Error Resume Next
        MkDir "C:\temp\"
        Kill "c:\temp\oledb_test.txt"
        On Error GoTo 0
        ' create the ADO connection
        Set objConnection = CreateObject("ADODB.Connection")
        ' set the connection string
        ' Using the Microsoft OLEDB Provider for Oracle works fine and dandy!
        'objConnection.ConnectionString = "Provider=MSDAORA.1;User ID=" & strUSER & ";Password=" & strPASSWORD & ";Persist Security Info=True;Data Source=" & strTNS_SERVICE_NAME
        ' But using Oracle Provider for OLEDB causes us problems!!
        objConnection.ConnectionString = "Provider=OraOLEDB.Oracle.1;User ID=" & strUSER & ";Password=" & strPASSWORD & ";Persist Security Info=True;PLSQLRSet=1;Data Source=" & strTNS_SERVICE_NAME
        ' set the cursor to open on the client
        objConnection.CursorLocation = 3    ' adUseClient
        ' open the connection
        objConnection.Open
        ' create the ADO recordset object
        Set objRecordset = CreateObject("ADODB.Recordset")
        ' set its active connection
        Set objRecordset.ActiveConnection = objConnection
        ' open it up, pulling in the data from the oledb connection
        objRecordset.Open "SELECT * FROM OLEDB_TEST"
        ' disconnect the recordset
        Set objRecordset.ActiveConnection = Nothing
        ' persist the recordset's data to XML
        objRecordset.Save "C:\temp\oledb_test.txt", 1       ' adPersistXML
        ' clean up our objects
        objRecordset.Close
        Set objRecordset = Nothing
        objConnection.Close
        Set objConnection = Nothing3) The resulting file in c:\temp\oledb_test.txt is as follows:
    <xml xmlns:s='uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882'
         xmlns:dt='uuid:C2F41010-65B3-11d1-A29F-00AA00C14882'
         xmlns:rs='urn:schemas-microsoft-com:rowset'
         xmlns:z='#RowsetSchema'>
    <s:Schema id='RowsetSchema'>
         <s:ElementType name='row' content='eltOnly'>
              <s:AttributeType name='RECORD_ID' rs:number='1' rs:writeunknown='true'>
                   <s:datatype dt:type='number' rs:dbtype='numeric' dt:maxLength='19' rs:scale='0' rs:precision='5' rs:fixedlength='true'
                    rs:maybenull='false'/>
              </s:AttributeType>
              <s:AttributeType name='RECORD_DESC' rs:number='2' rs:writeunknown='true'>
                   <s:datatype dt:type='string' rs:dbtype='str' dt:maxLength='50' rs:maybenull='false'/>
              </s:AttributeType>
              <s:extends type='rs:rowbase'/>
         </s:ElementType>
    </s:Schema>
    <rs:data>
         <z:row RECORD_ID='0'    RECORD_DESC='0     is OK!'/>
         <z:row RECORD_ID='1'    RECORD_DESC='1     is OK!'/>
         <z:row RECORD_ID='0'    RECORD_DESC='10    is wrong - comes out as 0'/>
         <z:row RECORD_ID='12'   RECORD_DESC='12    is OK'/>
         <z:row RECORD_ID='0'    RECORD_DESC='100   is wrong - comes out as 0'/>
         <z:row RECORD_ID='20'   RECORD_DESC='120   is wrong - comes out as 20'/>
         <z:row RECORD_ID='0'    RECORD_DESC='1200  is wrong - comes out as 0'/>
         <z:row RECORD_ID='230'  RECORD_DESC='1230  is wrong - comes out as 230'/>
         <z:row RECORD_ID='300'  RECORD_DESC='12300 is wrong - comes out as 300'/>
         <z:row RECORD_ID='2340' RECORD_DESC='12340 is wrong - comes out as 2340'/>
    </rs:data>
    </xml>Note that the RECORD_ID field is incorrect!! Somewhere along the line, for every 0 at the end of the RECORD_ID (when the RECORD_ID is not 0), a digit is removed from the beginning of the RECORD_ID!
    This is KILLING me!!!
    You will notice that there is a line of code that is commented out which uses the Microsoft OLE DB Provider for Oracle instead. This works fine and dandy. The trouble is I can't use it, as I need functionality in the Oracle provider that the MS provider doesn't have! OUCH!
    Can anyone confirm that they get the same problems, or is there something else in my system that is messing things up??
    Many thanks for any help!
    James
    Message was edited by:
    JAMES_2JS

    It does not affect VS2005. I tried this code on
    * Windows XP SP2 (with all the latest Windows Update Patches)
    * Oracle Data Access Client v10.2.0.2.20
    static void Main(string[] args)
        try
            // create connection
            string cnString = "Provider=OraOLEDB.Oracle.1;User ID=hr;Password=hr;Data Source=//localhost/xe";
            OleDbConnection conn = new OleDbConnection(cnString);
            // create and fill dataset
            OleDbDataAdapter da = new OleDbDataAdapter("select * from oledb_test", conn);
            DataSet ds = new DataSet();
            da.Fill(ds);
            // write to XML
            ds.WriteXml("c:\\temp\\oledb_test1.txt");
            // done
            Console.WriteLine("XML file created, press any key...");
            Console.ReadKey();
        catch (Exception ex)
            Console.WriteLine("Error: " + ex.Message);
            Console.ReadKey();
    }and the result is,
    <?xml version="1.0" standalone="yes"?>
    <NewDataSet>
      <Table>
        <RECORD_ID>0</RECORD_ID>
        <RECORD_DESC>0     is OK!</RECORD_DESC>
      </Table>
      <Table>
        <RECORD_ID>1</RECORD_ID>
        <RECORD_DESC>1     is OK!</RECORD_DESC>
      </Table>
      <Table>
        <RECORD_ID>10</RECORD_ID>
        <RECORD_DESC>10    is wrong - comes out as 0</RECORD_DESC>
      </Table>
      <Table>
        <RECORD_ID>12</RECORD_ID>
        <RECORD_DESC>12    is OK</RECORD_DESC>
      </Table>
      <Table>
        <RECORD_ID>100</RECORD_ID>
        <RECORD_DESC>100   is wrong - comes out as 0</RECORD_DESC>
      </Table>
      <Table>
        <RECORD_ID>120</RECORD_ID>
        <RECORD_DESC>120   is wrong - comes out as 20</RECORD_DESC>
      </Table>
      <Table>
        <RECORD_ID>1200</RECORD_ID>
        <RECORD_DESC>1200  is wrong - comes out as 0</RECORD_DESC>
      </Table>
      <Table>
        <RECORD_ID>1230</RECORD_ID>
        <RECORD_DESC>1230  is wrong - comes out as 230</RECORD_DESC>
      </Table>
      <Table>
        <RECORD_ID>12300</RECORD_ID>
        <RECORD_DESC>12300 is wrong - comes out as 300</RECORD_DESC>
      </Table>
      <Table>
        <RECORD_ID>12340</RECORD_ID>
        <RECORD_DESC>12340 is wrong - comes out as 2340</RECORD_DESC>
      </Table>
    </NewDataSet>

  • SQL Server OLEDB Provider Support Error - XL Reporter

    Hi forum,
    When i m trying to run the XL Reporter, It gives below given error.
    "Unable to Load SQL Server OLEDB Provider Resource DLL. The Application Can Not continue."
    I have remove Add-on folder, .sbo files and re-install too.
    Can any body guide the solution.
    With Regards,
    Chintesh Soni

    Hi Jim,
    Thnx for reply,
    We are using Windows XP Proff. SP2 on the machine. The machine is using as workstation.
    Warm Regards,
    Chintesh
    Edited by: Chintesh Soni on Dec 17, 2008 9:20 AM

  • SAP BW Multidimensional OLEDB Provider and NOPROMPT option

    Hello
    I'm trying to connect to a SAP system using the SAP BW oleDB provider with this kind of connection string:
    Provider=MDrmSap.2;Data Source=SAP VPN;Password=PASSWORD;User ID=USERID;Location="";Integrated Security=False;Persist Security Info=True;Impersonation Level=Anonymous;Mode=Read;Protection Level=None;Extended Properties="SFC_CLIENT=001;SFC_LANGUAGE=EN";Initial Catalog=$INFOCUBE;Prompt=4
    I use the "Prompt=4" parameter in order to prevent the driver from displaying any window.
    => I get this error:
    Authorization failed.
    I'am sure of the login.
    Moreover, if I remove the Prompt=4 parameter, a login box is displayed, then I just click OK, and the connection succeeds...
    code (C#):
    var conn = new OleDbConnection(theConnectionString);
    conn.Open();
    The currently installed version of SAP gui is
    SAP GUI for Windows 7.20 (Compilation 1)
    the version of mrdrmsap.dll (the "SAP BW DRM OLE DB for OLAP Provider") is 3.8.0.4
    Has anyone already encountered this behaviour please?
    I know this used to work with a previous version of the SAP Client.
    Is it a known problem with this specific version of the SAP client ?
    Thanks in advance for any information,
    Mary.

    Hi Nikee,
    can you make sure the OLAP BAPI component from the SAP Integration Kit is installed on the BusinessObjects server ?
    thanks
    ingo

  • How to add spaces at the end of record

    Hi Friends,
    i am creating a file which contains more than 100 records.
    In ABAP i have internal table with on field(135) type c.
    some time record have length 120, somtime 130 its vary on each record.
    but i would like to add space at the end of each record till 135 length.
    Can you please help me how to add speace at the end of record.
    regards
    Malik

    So why did you said that in your first posting? My glass sphere is out for cleaning...
    Instead of type c use strings and add spaces until they have the appropriate length.
    loop at outtab assigning <pout>.
      while strlen( <pout>-val ) < 135.
        concatenate <pout>-val `` into <pout>-val.
      endwhile.
    endloop.

  • Add spaces in XML tag in XI mapping

    Hello guys,
    In an IDoc to XML file scenario within XI, we want to add spaces at the end of an IDoc field that contains text description. When the IDoc gets generated on SAP ECC, the IDoc field is repeated so many times until all the contents are displayed, separated with spaces. However, once the IDoc is sent to XI, the spaces get lost. Is it possible to add a space at the end of each field presence within XI message mapping or they will get lost again ?
    Thank you.
    Best Regards,
    Evaggelos Gkatzios
    Edited by: Evaggelos Gkatzios on Nov 12, 2010 4:49 PM

    > In an IDoc to XML file scenario within XI, we want to add spaces at the end of an IDoc field that contains text description.
    The way IDoc processing works, that does not make any sense at all.
    An IDoc is a fixed length container and the fields are filled with spaces automaticically.
    The IDoc XML generation removes trailing spaces to reduce message size.
    If you need trailing spaces in an XML field, you can add them easily with a UDF. But I think that there are only rare scenarios where you really would need this.

  • How to add space between two tabs in accodion widget?

    Hi! I am using the accordion widgets and trying to add space between each of the tabs, would someone help me on this. Thanks

    Directly editing the output of Muse is virtually always a bad idea. At a minimum it will create a very cumbersome workflow since Muse will overwrite your changes every time you re-export (export, upload, publish, preview).
    It depends on exactly what visual effect you want to achieve, but you probably just need to select the accordion widget and use the Spacing panel to adjust the vertical gutter value.

  • Differences between Oracle OLEDB Provider & Microsoft version

    I am trying to connect to an Oracle database from a SQL Server SSIS package. When I use the Microsoft OLEDB Provider for Oracle (MSDAORA) the connection manager in the package sees a full list of the tables in the Oracle database but when I use Oracle's own OLEDB provider (Oracle.OLEDB.1) I see a much smaller list. I cannot see anything different about the tables that Oracle's Oracle provider fails to see. Has anyone come across this phenomenon before ? Are there some table name characters or data types that the Oracle provider objects to ?

    Not very likely.
    One possible explanation is they query different levels of the datadictionary.
    Sometimes the ALL_ level is queried, sometimes the DBA_ level, sometimes the USER_ level.
    At least you need to ascertain whether you are using the same Oracle account in both drivers. This can also make a difference.
    Anyhow: usually the Oracle driver implements way more functionality compared to the Microsoft driver, so the Oracle driver is to be preferred anyway.
    And probably the Oracle drivers results are correct (one really should use the ALL_ level instead of the DBA_ level).
    Sybrand Bakker
    Senior Oracle DBA

  • Upgrade OLEDB provider

    Hi,
    We found a bug in Oracle OLEDB Provider what released with 11g (R1 or R2) client.
    It give size of text type columns (e.g. nvarchar2) wrongly (double size as it is in character).
    I found that 11.2.0.3 version of it was repaired and free of this bug.
    It is part of ODAC 11.2.0.3, but I can not install it to remain the oracle client properly working.
    Net Manager disappear (freeze with close) when I push 'test' button during create a new net service.
    So my question is:
    how can I upgrade OLEDB provider (e.g. with new ODAC installation) and the client tools (net manager, SQL* Plus)
    remain working?
    In previous versions (as I remember 9i, 10g) it was not problem to install ODAC into the same oracle home.
    I had try to install it into new oracle home, but it result to the same.
    Regards,
    Imre

    You may want to back up your packages, then use a simple text editor to search and replace in your DTSX packages...
    Talk to me now on

  • Oracle OLEDB PRovider with ASP

    hi,
    Can anyone provide me a piece of code which demonstrates how to call an Oracle sp from asp using the Oracle OLEDB provider.
    I would also appreciate if the Oracle package code could be provided too, since with the Provider we have to have a different code for the stored procedure (Ref cursor..??)
    I have been successfully connecting using the Microsoft ODBC Driver, but looks like it has some big time bugs in it which causes our server to hang and a dllhost.exe to consume large amounts of database memory.
    Anybody can help me with that?
    Many Thanks,
    Harshad.

    Harshad,
    Oracle OLEDB samples are available at
    http://otn.oracle.com/sample_code/tech/windows/ole_db/content.html
    URL.
    "Returning multiple recordsets from a stored procedure" sample demonstrates
    how REF cursors are returned from a Stored Procedure (contained in a DB package).
    This sample is a stand alone application and not an ASP program, but the same code
    can be helpful for ASP too.
    Regards
    Jagriti

  • Oracle.Oledb provider returning improper out-put

    Dear All,
    Need your help in below issue.
    I have SSIS package which pull data from Oracle to SQL Server.
    Currently I have used Oracle.Oledb provider for the same, but it is giving me improper result.
    I check on oracle end count for that table was 26000 and when I run the same query through SSIS it shows 0 rows.
    The preview of the query is showing 0 as output.
    but when I tried the same using Microsoft OLEDB provider for Oracle it giving me proper out-put

    Hi Sushant,
    UseSessionFormat - specifies whether to use the default NLS session formats or let OraOLEDB override some of these formats for the duration of the session. Valid values are 0 (FALSE) and 1 (TRUE). The default is FALSE which lets OraOLEDB override some of
    the default NLS session formats. If the value is TRUE, OraOLEDB uses the default NLS session formats.
    Setting UseSessionFormat=true in the connection string will result in the provider using the session format specified by the client install, which should resolve this issue. The following connection string for the connection like below:
    Data Source=DataSourceNameHere;User ID=UserIDHere;Password=PasswordHere;Provider=OraOLEDB.Oracle.1;Persist Security Info=True;UseSessionFormat=True;
    Reference:
    http://blogs.msdn.com/b/dataaccesstechnologies/archive/2012/01/20/every-bug-is-a-microsoft-bug-until-proven-otherwise.aspx
    Thanks,
    Katherine Xiong
    Katherine Xiong
    TechNet Community Support

  • Oracle OLEDB Provider

    Good Afternoon:
    I am having trouble running sql thru VB with the
    Oracle OLEDB provider. The sql runs fine with the
    MSDAORA provider. My error is 'missing right parenthesis'.
    Here is the sql:
    SELECT b.DIVISION_ID KEY, b.PLAN_TYPE PLAN, 900000 FS_CODE,
    SUM (CASE WHEN NOT (d.PHARMACY_NETWORK_CODE IN ('9003','9004','9012') and b.CORPORATION_ID NOT IN ('U120','U180'))
    then a.NET_CHECK_DUE_AMT/c.COMPLETION_FACTOR else 0 end) IN_PAY,
    TRUNC (a.SERVICE_DATE,'YEAR') INCURRED_YEAR, SYSDATE
    From PHARMACY_FACT a, PLAN b, COMPLETION_FACTOR c, PHARMACY_CLAIM_GROUPING d
    Where a.PLAN_KEY = b.PLAN_KEY
    AND a.PHARMACY_CLAIM_GROUPING_KEY = d.PHARMACY_CLAIM_GROUPING_KEY
    AND c.FINANCIAL_SERVICE_SUBGROUP = 900000
    AND c.MONTH_INTERVAL = MONTHS_BETWEEN(TRUNC(TO_DATE('09/30/2003','MM/DD/YYYY'),'month'), TRUNC(a.SERVICE_DATE,'MONTH'))
    AND a.SERVICE_DATE BETWEEN TO_DATE('01/01/2000','MM/DD/YYYY') AND TO_DATE('07/31/2003','MM/DD/YYYY')
    AND a.PAYMENT_DATE BETWEEN TO_DATE('01/01/2000','MM/DD/YYYY') AND TO_DATE('09/20/2003','MM/DD/YYYY')
    AND b.PLAN_NBR NOT IN('R1','V1','V2') AND b.CORPORATION_ID IN('F275', 'P475')
    GROUP BY b.DIVISION_ID, b.PLAN_TYPE, TRUNC(SERVICE_DATE,'YEAR')
    When I comment out the case statement, sql runs.
    I tried putting parens around other parts of the
    statement but to no avail.
    Any help would be greatly appreciated.
    Thanks,
    Mike

    Sounds like the bug 2597418 that was fixed and released in 9.2.0.2 of Oracle OLEDB Provider

  • Oracle OleDB Provider VS MS OleDB Provider

    I am using Stored Procedures in Oracle Packages and Microsoft ADO for data access.
    My Stored Procedure use a Ref Cursor output parameter to make data available to ADO's recordsets.
    A big difference in network traffic is found between "Microsoft OLEDB Provider for Oracle" and "Oracle OLEDB Provider" (the native driver provided by Oracle).
    The main issue :
    <<Oracle OLEDB Provider>>
    1) A stored procedure is put into an empty package for testing and returning no row, the result is 4KB downstream traffic.
    2) When the SAME stored procedure is put into a large package (a package that already contained 30 other stored procedures, > 1000 lines codes), the result is 70KB downstream traffic for same call that return no row.
    <<Microsoft OLEDB Provider>>
    1) and 2) both use approximately 4KB downstream traffic.
    However, for a query that return large number of rows (~2000 rows), Oracle OLEDB Provider used 143KB but MS OLEDB Provider used 400KB downstream.
    The behaviours for upstream are similar.
    My application is required utilize limited bandwidth, the the strange behaviour of the Oracle OLEDB Provider make my development of "Packaged" Stored Procedures a big problem.
    Does anyone know if there are any tricky on the Oracle OLEDB Provider? Please advice, thanks in advance.
    Regards,
    Jeff

    Sounds like the bug 2597418 that was fixed and released in 9.2.0.2 of Oracle OLEDB Provider

  • Oracle connect failed on x64 and IA64 platform via Oracle OLEDB provider

    Hi everyone,
    I installed SQL Sever on x64 and IA64 machine, and Create a database via Oracle datasource. I can connect the datasource via OLEDB and .Net provider successfully on x86 machine. But failed to connect the Oracle datasource on x64 and IA64.
    Following is the error messgae:
    1) Install 64 bit build on x64 machine:
    Error message: Test connection failed because of an error in initializing provider. ORA-06413: Connection not open.
    2) Install 32 bit build on x64 machine:
    Error message: Test connection failed because of an error in initializing provider. Oracle client and networking components were not found. These components are supplied by Oracle Corporation and are part of the Oracle Version 7.3.3 or later client software installation.
    I know there is a know bug on c:\Program Files (x86)\... with Oracle provider. And some one has given a workarround method that I should move my my application out of the the folder path which includes parentheses. But it really is mess method for SQL Server (That is my application)......
    Is there any other workarround method? Or when will Oracle fix this bug?
    Thanks^_^
    Lindsay

    Is 10204 available for x64 and IA64. It is said that there is only 10204 for x86 machine, right?
    I downloaded 10203 for IA64 machine and tested connection on SQL Server with Oracle datasource via Oracle OLEDB provider, and got the following error (The data source is Oracle92 installed on another machine):
    Test connection failed because of an error in initializing provider. Oracle client and networking components were not found. These components are supplied by Oracle Corporation and are part of the Oracle Version 7.3.3 or later client software installation.
    Could you please tell me what's wrong with it?
    Thanks
    Lindsay
    Message was edited by:
    lindsaywang

Maybe you are looking for