Microsoft Ole Db Provider For Oracle Error In Initializing Provider
Contents |
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered test connection failed because of an error in initializing provider. ora-12154 by: Test connection failed because of an error in initializing provider. test connection failed because of an error in initializing provider ssis sql server Oracle client and networking components were not found. These components are supplied by Oracle Corporation and are test connection failed because of an error in initializing provider. unspecified error part of the Oracle Version 7.3.3 or later client software installation SQL Server > SQL Server Integration Services Question 0 Sign in to vote I am facing the oracle client and networking components were not found ssis error while connecting to oracle server from SSDTBI 2012 SSIS package. I installed Oracle 11g client and adapter "AttunitySSISOraAdaptersSetupX64". But still getting the same error: "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
Test Connection Failed Because Of An Error In Initializing Provider Oracle Ssis
Version 7.3.3 or later client software installation.Provider is unable to function until these components are installed." Can anybody suggest me the solution . Thanks Bikram Thursday, October 23, 2014 12:26 PM Reply | Quote Answers 0 Sign in to vote Hi Bikram, SSDT (SQL Server Data Tools) is only a 32-bit application. If the 64-bit Oracle client is installed but SSIS is being executed with the 32-bit dtexec executable, SSIS will not be able to find the Oracle client. So the error occurs. In order to fix this issue, please install the 32-bit Oracle client side-by-side with the 64-bit client. For more details, please refer to the following blog: http://sqlblog.com/blogs/jorg_klein/archive/2011/06/09/ssis-connect-to-oracle-on-a-64-bit-machine.aspx Thanks, Katherine Xiong If you have any feedback on our support, please click here.Katherine Xiong TechNet Community Support
Marked as answer by Katherine XiongMicrosoft contingent staff, Moderator Tuesday, October 28, 2014 1:13 AM Friday, October 24, 2014 8:35 AM Reply | Quote Moderator 0 Sign in to vote Hi, Now the connection problem solved. I uninstall- Connect to Oracle on a 64-bit machine (Updated for SSIS 2008 R2) We recently had a few customers where a connection to Oracle on a 64 bit machine was necessary.
Oracle 11g Full Client
A quick search on the internet showed that this could be a big problem. I microsoft connector for oracle by attunity found all kind of blog and forum posts of developers complaining about this. A lot of developers will recognize the following error message: ssis oracle connection 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 https://social.technet.microsoft.com/Forums/windowsserver/en-US/a8ea0355-af52-4973-8797-61dadcdbc0a2/test-connection-failed-because-of-an-error-in-initializing-provider-oracle-client-and-networking?forum=sqlintegrationservices installation. Provider is unable to function until these components are installed. After a lot of searching, trying and debugging I think I found the right way to do it! Problems Because BIDS is a 32 bit application, as well on 32 as on 64 bit machines, it cannot see the 64 bit driver for Oracle. Because of this, connecting to Oracle from BIDS on a 64 bit machine will never work when you install the 64 http://sqlblog.com/blogs/jorg_klein/archive/2011/06/09/ssis-connect-to-oracle-on-a-64-bit-machine.aspx bit Oracle client. Another problem is the "Microsoft Provider for Oracle", this driver only exists in a 32 bit version and Microsoft has no plans to create a 64 bit one in the near future. The last problem I know of is in the Oracle client itself, it seems that a connection will never work with the instant client, so always use the full client. There are also a lot of problems with the 10G client, one of it is the fact that this driver can't handle the "(x86)" in the path of SQL Server. So using the 10G client is no option! Solution Download the Oracle 11G full client. Install the 32 AND the 64 bit version of the 11G full client (Installation Type: Administrator) and reboot the server afterwards. The 32 bit version is needed for development from BIDS with is 32 bit, the 64 bit version is needed for production with the SQLAgent, which is 64 bit. Configure the Oracle clients (both 32 and 64 bits) by editing the files tnsnames.ora and sqlnet.ora. Try to do this with an Oracle DBA or, even better, let him/her do this. Use the "Oracle provider for OLE DB" from SSIS, don't use the "Microsoft Provider for Oracle" because a 64 bit version of it does not exist. Schedule your packages with the SQLAgent. Background information
Early Adopter Program ArcGIS Ideas Esri Support Services ArcGIS Blogs ArcGIS Code Sharing Product Life Cycles Manage http://support.esri.com/technical-article/000002581 Cases Request Case Start Chat Back to results Print Share http://dba.stackexchange.com/questions/115264/oracletest-connection-failed-because-of-an-error-in-initializing-provider-ora Is This Content Helpful? Search on GeoNet Submit to ArcGIS Ideas Error: Test connection failed because of an error in initializing the provider Error Message When using the Microsoft OLE DB provider for Oracle to establish a error in connection to an Oracle database in ArcCatalog, if the network service name is incorrectly entered in the Data Link Properties menu, the following error is returned:"Test connection failed because of an error in initializing the provider. ORA
log in tour help Tour Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Database Administrators Questions Tags Users Badges Unanswered Ask Question _ Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Oracle:Test connection failed because of an error in initializing provider. ORA-12170: TNS:Connect timeout occurred up vote 0 down vote favorite We have Migrated SQL server 2008R2 to SQL server 2012 from Windows 2008R2 onto Windows 2012R2. Everything went well , except for the Oracle database connection: We have a SSIS package created on SQL server 2008R2(fetches the data from Oracle DB) and while testing its connection (on newly migrated server) with Oracle database (on other server) initially we got the error below, (when oracle database client was 12c on windows 64 bit platform) 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. Provider is unable to function until these components are installed. As per the Link here we came to know that Because BIDS is a 32 bit application, as well on 32 as on 64 bit machines, it cannot see the 64 bit driver for Oracle. Because of this, connecting to Oracle from BIDS on a 64 bit machine will never work when you install the 64 bit Oracle client. Hence , we went with installing both 32 bit and 64 bit Oracle 12 C client : But after installing, when we tested the connection via SSIS package, we get error saying " Test connection failed because of an error in initializing provider. ORA-12170: TNS:Connect timeout occurred" Since i do not have much expertise on Oracle, need experts guidance on this to fix the issue. Any suggestions would be very helpful. s