I installed Oracle 12 ODAC(with ODT) on two computers.
I notice two things :
The program doesn't appear in the "Windows program list" mainly used to remove/modify installed applications (only 40MB for documentation). Bad stuff, but why not...
Visual Studio is not aware about the installation and when I want to add a database connection by Tools/Connect to Database...", the new Oracle providers is not showned. VS asks for at least an Oracle 7, none is registered ! Like before to install Oracle product :(
My needs are basic, I'm quite surprise the Oracle setup has a strange behavior and doesn't seem to be fully registered.
Any idea about a missing stuff ?
Thanks by advance all,
Nd.
PS : I need a rest tonight, I'll be back tomorrow :)
I remember vaguely struggeling with the same issue. I went back to download and install the Oracle ODP.NET. That provided a setup to handle Visual studio integration and works fine for me. (Currently using ODP11.2.320)
Related
I installed Windows 10 on my Lenovo T540p laptop. Nothing special of course. I work as a developer, so I also installed Visual Studio 2019, SQL Server 2019 and Oracle 19 c.
Now, most of my work is done on SQL Server, but I do have 1 or 2 clients which use Oracle, requiring me to have a working Oracle instance on my machine.
But... I only need it like 10% of the time, so ideally I would like to configure the Oracle services so I can manually start them when I need it.
Been playing around with this in the past, but it appears simply putting the services on manual isn't enough.
Googling this question gave me a couple of ideas on how to manually start up a db, but besides 1 question here I didn't actually found anything (even partialy) usable. Anyone here who can tell me how to best pull this off?
Want to use an Oracle-ODBC connection in Visual Studio 2017/ SSIS as it's much faster than OLE DB during tests.
Problem:
I follow Oracle's steps to the letter.
Install instant client (v18, also tried v12).
Download/ extract ODBC download in same library. Run odbc_install.exe.
See the Driver in 'ODBC Data Sources/ Admin' in Windows 10.
Add new User Data Source. TNS Service names pull up fine. Test
Connection (User/ Pass) -- it works!! The Connection works!!
I tried this with 64 bit in Oracle, their instant client v18.3 or 12.2 both. All works in Window's "Oracle Source Administrator" via test connections.
I tried this with 32 bit downloads as well. All is good.
Now, open Visual Studio. First tried 64 bit (my Windows OS is 64 bit, but Visual Studio Data Tools is only 32 bit). Had a hunch it wouldn't work.
Error message "system architecture and client is not the same" or such. Gotcha.
Tried the 32 bit Oracle ODBC driver (User Source). I keep getting the same message (tried 18_3 and 12_2 versions).
Now .... SQLORA32.dll is in the very file path it named. It's right there! Why can't it be found? The test connection in ODBC Source Admin works! What is going on here?
And I'm unsure if I have to "register" something via the command line, I had to do that once before, maybe it was an unrelated issue.
To boot, when I tried a 3rd party "Devart Oracle ODBC connector" -- it's a simple 5-second install wizard that works flawlessly instantly. Problem is it's a 30-day trial and costs $150 at least. How can I can get an Oracle-created ODBC connector (Oracle being world-renowned for janky-azz products) to actually work?
Devart, and probably Attunity Oracle ODBC: 5 second installs
Oracle's own: Harder to install than breaking into Fort Knox/ learning Mandarin Chinese. Please advise.
I am answering my own question.
Unfortunately some of us ETL/ BI guys need to go so wide on problems that there's no time to figure out every little detail/ glitch of Oracle's ... whatever they're doing now.
But here's a fix. In Visual Studio 2017/ Data Tools/ the SSIS IDE .... if you want an Oracle ODBC connection (Faster than OLE Db for some reason) --- when you're setting it up, instead of selecting a NAMED "user or system data source" that you created in ODBC Source Administrator, simply using the "Builder" option (to the left of Use Connection String) for a connection string. It does the exact same steps as the ODBC Source Admin, but within Visual Studio. I don't know what the difference is here, but some wizardry/// who knows what is different, and the connection somehow, suddenly, for some reason, works.
we have tested WAS 7 migration into 8.5 by using the migration.sh script and everything seemed to go fine but we have lost the graphical management of the servers and applications (not of the AdminAgent: that works fine).
Has anyone experienced something similar?
Usually prior to getting to this screen
you need to choose between
Well, as a consequence of our mistaken migration we now access directly to the above one, i.e. waspro1ANode01 (Admin Agent) but have lost the other one and all our trials to recover it have been unsuccessful.
Please, any help is most welcome !!!
We have one user (a developer) who is experiencing issues with Oracle DataAccess based on whether they are setup as a local administrator on their PC or not.
I dont know the inner workings of Oracle, so im really struggling to figure this one out. My research seems to suggest the problem is around the oracle.dataaccess.dll and maybe linked to the fact that they have Visual Studio 2012 installed.
If the user is configured as a local administrator on thier PC, and they try to run an application they get the following error:
'Object reference not set to an instance of an object.
Source: Oracle.DataAcess.GetData.GetUserPermissions.wsMS_load
If they are NOT an administrator, the application runs (but they have other problems related to not being as admin - they need admin permissions).
I have a feeling it is something to do with Oracle trying to look at the incorrect version of the .dll. I have read some things about accessing the GAC and getting Oracle to reference a different version of the .dll, but as this stuff does not mean a lot to me I am getting out of my depth.
Your help is appreciated!
I have seen problems with running as admin -vs- a restricted account in the past.
The problems I have seen are related to permissions of oracles install directory on the machine. The quickest way to test for this problem is to tnsping your database using both users on the machine.
If one of them fails they most likely don't have rights to see libraries and config.
However, I have never seen this error message in association with this.
I would have the developer narrow down his code to a few lines that reproduce the problem and then edit the question with those lines. It would greatly increase your chances of get a resolution to the problem.
I had the exact same problem with a VS 2012 and oracle.dataAccess.dll In a software my team developed. When looking dipper to the code and spending lots of hours configuring all kinds of stuff eventually turns out it was a compiling error due to a 64x/86x bit mismatch. Your exception is quite general but I hope this works for you too.
I'm trying to install Oracle BIEE 11g on my computer, but something wiered happend.
I've tried on a x86 computer with 2GB memory and a x64 computer with 4GB memory. Both of them are running Windows OS. I want to connect a MS-SQLSERVER database, and I've finished creating related DEV_ tables using RCU.
I followed the tutorial from the doc.oracle.com, but then I stopped at the 14th step, it says "设置数据库连接失败". I can continue install, but another error occurs, service obisch1 cannot start. I can open localhost:9704 after installation, but it will return a 500-error after I restart my computer.
I searched the internet, it says I should set my database source using "Net Manager" Tool, but I don't know how. And after install I got a database source using driver "MERANT OEM 5.3 32-BIT SQL Server Wired Protocol", but I can't make change to it, cause the system says can't find the driver...
I don't know what to do now... Anybody can help me? Thanks very much.
Well, I've kind of solved it.
I still don't know why my computer cannot find the odbc drier "MERANT OEM 5.3 32-BIT SQL Server Wired Protocol", which seems to be the reason why I can't connect to the database at the 14th step while I install OBIEE.
However, I add an odbc-connect through the system's function, I found it in the control panel.
On the other hand, the url http://localhost:7001/em and http://localhost:7001/analytics can be still accessed(after a long time, it can be accessed).
So, then I create a rpd file use my own odbc-connect, and it seems work fine.
Thanks everybody, anyway, and hopes can help