This content has been marked as final. Show 7 replies
Please tell us what "didn't work" - what error message did you get ?
with 11g tnsnames.ora file will be under asinst_1/config directory. Copy there and you can connect
I think a better solution would be to create a TNS_ADMIN environment variable and point to a single instance of the "tnsnames.ora" file. By using the environment variable, all instances of Oracle will see this variable and use it. The other option would be to add the TNS_ADMIN key to your registry, but with this option you have to add the key to each Oracle Home. Consequently, I like the environment variable better! ;)
Hope this helps,
If someone's response is helpful or correct, please mark it accordingly.
Craig , Idea is good , but you need to have different settings for Forms runtime then. Forms 11 runtime by default picks up TNS_ADMIN from default.env, which points to instance_home/config directory.
Thanks a lot. When I added my db details in tnsnames.ora at asinst_1\config it worked.
I have the same setup as the user stated above and have moved my tnsnames.ora from my 10g Dev environment to asinst\config folder and I still can't connect. The error says that the listener doesn't know of the service in the connect descriptor, however when looking at the status of the lsnrctl, it shows that the service is registered. Is there any other kinds of configuration (ie, file locations) that may be different for forms 11g?
I had the same error: ORA-12514 after installing this.
I am using the loopback adapter with the hostname to install Forms11gR2 and
then I changed 'localhost' with 'hostname' in the listener.ora and tnsnames.ora.
You have to copy the tnsname.ora and sqlnet.ora to ..\asinst_frm\config and +\Oracle_FRHome1\network\admin+
Now I can work with Forms10g, Forms11gR2 and DB 11.2.03. on the workstation.
I hope it helps.