2 Replies Latest reply on Apr 12, 2006 2:36 AM by 505045

    can't use oracle data provider for .net

      I just installed the odp.net package so I can use the .net provider (oracle data provider for .net). I wanted to use that dataprovider as a connection manager in Sql Server Integration Services but when I open the "Connection Managers" window all I can see is this

      On the 'connection' pane im redirected to the 'all' pane and there I'm not able to fill in anything. Anyone seen this before? Anyone who knows what can be going wrong?

        • 1. Re: can't use oracle data provider for .net
          Your using it wrong Oracle is different. When you installed the ODP.NET your post to connect to your Database. You can check using Oracle Connection Manager or something like that. There should be a test connection under the menu. I dont have Oracle on my Lab Top so bare my briefiness.

          Once you have a connection. Then you must add the Oracle Assembly to the Web.Config.

          Then add the assembly to your class (e.g. using Oracle.DataAccess.Client;)

          Then you will need the connection string (e.g. OracleConnection con = new OracleConnection("User Id=sdf;Password=sdfds;Data Source=ora_sid_name");)

          The hardest part is finding the Oracle Assembly and then adding to the Web.Config I used the command prompt and some command I found in my book that shows a list of all the assemblies. If you got VS.NET it is very easy just say Add Web Reference or Add Assembly and find the Oracle.DataAccess assembly and then add it to project and check the web.config file that is what you are missing.

          Hope that helps

          Recap Connect using Oracle Client Connection to Oracle Database then
          add reference to assembly and then include the namespace Oracle.DataAccess.Client;
          • 2. Re: can't use oracle data provider for .net
            Here are the assemblies
            <!-- For the Old Visual Studio.NET 03 Tool -->
            <add assembly="Oracle.DataAccess, Version=, Culture=neutral, PublicKeyToken=89B483F429C47342"/>

            <!--for the new Beta .NET v2.0 -->
                                <add assembly="Oracle.DataAccess, Version=, Culture=neutral, PublicKeyToken=89B483F429C47342"/></assemblies>

            stick in the Web.config


            <?xml version="1.0"?>
                      <!-- Oracle connection-->
                      <add key="OraString" value="User Id=schema;Password=password;Data Source=uni"/>
                      <add key="SequelUNI" value="Trusted_Connection=Yes;data source=server02;persist security info=False;initial catalog=uni;"/>
                      <pages enableViewState="true" enableViewStateMac="true"/>
                      <!-- validation="[SHA1|MD5|3DES]" -->
                      <machineKey validation="3DES"/>
                      <authentication mode="Windows"/>
                           <allow users="SERVER02\Administrator"/>
                           <!--* All Users and ? all unauthenticated users -->
                           <!-- Deny all anonymous users -->
                           <deny users="?"/>
                      <!-- <identity impersonate="true" userName="s" password="s" /> -->
                      <identity impersonate="true"/>
            Set compilation debug="true" to insert debugging
            symbols into the compiled page. Because this
            affects performance, set this value to true only
            during development.
                      <compilation debug="true">
                                <add assembly="Oracle.DataAccess, Version=, Culture=neutral, PublicKeyToken=89B483F429C47342"/>
                                <add assembly="Oracle.DataAccess, Version=, Culture=neutral, PublicKeyToken=89B483F429C47342"/></assemblies>
            The <authentication> section enables configuration
            of the security authentication mode used by
            ASP.NET to identify an incoming user.
            The <customErrors> section enables configuration
            of what to do if/when an unhandled error occurs
            during the execution of a request. Specifically,
            it enables developers to configure html error pages
            to be displayed in place of a error stack trace.

            <customErrors mode="RemoteOnly" defaultRedirect="GenericErrorPage.htm">
            <error statusCode="403" redirect="NoAccess.htm" />
            <error statusCode="404" redirect="FileNotFound.htm" />