August 14, 2015 at 12:17 pm
Just install a new SQL server 2014 instance.
And install Oracle 12 c OLEDB driver from Oracle client.
Create a new SSIS package, and tried to create a new Oracle connection manager, right after I input username and password, the SSDT_BI tool which is the Visual studio 2013 shell crashed.
Any help please?
THanks
August 14, 2015 at 12:24 pm
Did you try it a 2nd time?
For best practices on asking questions, please read the following article: Forum Etiquette: How to post data/code on a forum to get the best help[/url]
August 14, 2015 at 12:34 pm
I uninstalled both Oracle 32 bit and 64 bits client ( I only installed the OLEDB driver and ODBC driver) totally from my windows machine, clean up the directories. reboot machine,
And now I only install 32 bits Oracle OLEDB driver, right after I open visual studio shell 2013 for a SSIS package, and create a OLEDB connection manager using Oracle provider, input user name and password, click Test connection, visual studio crashed, it gave the regular error message of :
Check online for a solution and restart the program, restart program, debug the program.
Thanks for any advice.
August 17, 2015 at 8:21 am
Did you try a reboot after installing the oracle clients?
Is the oracle client the latest from oracle support?
August 17, 2015 at 9:42 am
I tried to reboot the server multiple times.
I ended up clean up all the oracle client, including registry. And then start over to install something different. ODAC.
It finally works.
August 18, 2015 at 11:21 am
I had a this problem with oracle client and SQL Bids Debugger (wich runs VS 2010 32 bit version). i think it has something to do with the 32 bit oledb driver used in design but the ssis debugging package properties are set to 64 bit execution which cause it to crash. Went through all the uninstall and install as you did.
I only installed the win32_11g client to work.
August 18, 2015 at 11:56 am
Actually I don't have problem with installing 32bits and 64bits drivers in one oracle home.
It works for both VS and 64 bits (like SQL agent to run SSIS package.)
I do custom install, only drivers and SQLplus , not the entire client.
The error only occurs to me for 12c client install when I do the same way as 11g2.
Finally I got it work using ODAC install, both 32 bits and 64 bits.
Viewing 7 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy