February 27, 2014 at 1:14 pm
Anybody have good references that can guide me through this process? I'm trying to set up a connection from SSIS VS 2008 selecting ADO.NET/.Net Provider/OracleClient Data Provider and putting in the server name and username and pw and when I click on "Test Connection" I get this message. "ORA-12504: TNS:listener was not given the SERVICE_NAME in CONNECT_DATA"?
Here's a little context of my set up. My machine is a 64bit and the server that has the Oracle DB is also 64bit. I'm running Win 7 Enterprise. The Oracle server is Win 2008 r2 standard.
February 28, 2014 at 12:26 am
Did you install the Oracle Client and the ODAC components?
Did you configure TNSNAMES.ORA?
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
February 28, 2014 at 10:06 am
I believe so not 100% sure. How can I verify I did? I can tnsping the Oracle server fine and I have sqldeveloper connecting to the Oracle server from my machine fine. TNSNAMES.ORA on the Oracle server is configured.
February 28, 2014 at 1:42 pm
I got it to work, but now when I try and query the table in Oracle it says the table does not exist? But, I see the table on SQLDeveloper. Anybody know why?
March 3, 2014 at 9:58 am
Maybe you need to prefix the schema to the table?
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
March 3, 2014 at 1:01 pm
Found out it was a quoted identifier issue. Needed to write the table with double quotes around it. Interesting thing though is I also recreated the package with a different table name and it worked just fine.
select * from "test2".
Viewing 6 posts - 1 through 5 (of 5 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