ODP.NET installed but now I think there might be two oracle homes? cannot connect anyway....

Hi,

I was trying to install ODP.NET there, and that went ok. It installed to E:\oracle\product\10.2.0\client_1... But, the thing is I already have an oracle home under E:\oracle\ora92

So, I can connect OK using the ODACHome1 using TOAD and I can connect to the original home ORAHome92 ok. However, when I try it through code I get an error 'ORA-12154: TNS:could not resolve the connect identifier specified'.

I think this is probably because the default home is ORAHome92 and probably I need to set it to ODACHome1. Or, somehow I need to specify that the ODP.NET code should use ODACHome1. Well, I'm just guessing there really. What should I do to fix this? (I'm using VS 2005; VB.NET)

Thanks Aiden
AidenAAsked:
Who is Participating?
 
johnsoneConnect With a Mentor Senior Oracle DBACommented:
Within the original home, there should be a tnsnames.ora file.  If you copy that file to the new home, in the same place (the network\admin directory), that should let you use either home directory.
0
 
AidenAAuthor Commented:
Hi thanks, yes i tried that but it didn't work. Are you sure that the default home being the wrong one isn't a problem?
0
 
johnsoneSenior Oracle DBACommented:
The ORA-12154 error would indicate that something is incorrect with the tnsnames.ora file, or the connect string.

You should be able to change the default home with the home selector utility.
0
Cloud Class® Course: Microsoft Azure 2017

Azure has a changed a lot since it was originally introduce by adding new services and features. Do you know everything you need to about Azure? This course will teach you about the Azure App Service, monitoring and application insights, DevOps, and Team Services.

 
AidenAAuthor Commented:
ok but tnsnames.ora was working fine absolutely no problems until i just installed ODP.NET. so clearly that changed something. Now, even if I try and use my previous method of connecting (OraOLEDB.Oracle) it is producing this error. I'll have a check about this home selector but if i look at the environmental variables they show:

E:\oracle\product\10.2.0\client_1\bin;E:\oracle\ora92\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;

as the first few environmental variables... I tried to remove the first one just to see if i could connect as i did before the installation... but no luck...
0
 
AidenAAuthor Commented:
ok this is starting to get bad. still trying to just get my original connections working and now getting a The 'OraOLEDB.Oracle' provider is not registered on the local machine

think i'm just going to try and uninstall ODP.NET...
0
 
slightwv (䄆 Netminder)Connect With a Mentor Commented:
Oledb error is like a PATH issue.  Put the old home in the path first.

For the tns error: set an environment variable TNS_ADMIN pointing to the folder with the correct tnsnames.ora file.

I would suggest the env var as a test.  Once you get it working we can get the file in the proper place.
0
 
AidenAAuthor Commented:
i was busy on something else there... but will start back on this on friday i think... and I think also i'll have to go with ODP.NET after all since I inadvertently convinced others to go with it to!

the OraOLEDB.Oracle started working by itself i think just after i turned off the machine and came in the next day... so I just need to get ODP.NET working again... i'll let you know how I go on that and check your suggestions
0
 
AidenAAuthor Commented:
actually i managed to solve this issue but can't remember how exactly... i think it might have just been a coding issue. Either way I'll just close off this question and won't add to knowledge base...

thanks for help...
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.