Ora-12546 tns permission denied during installation

Other machines are in which network, same as your database network? In that case you should be able to connect if you are into this network using VPN. If "other machines" are in a different network through VPN or by any other means , they would probably not able to connect. Your network admin may explain it to you in a better way.

Thanks for the quick reply. The other machines are in the same corporate network, but the machine with the databases is connected to the network through the VPN. Some of the other machines are also connected to the network through a VPN connection and some are on the network directly. But once the VPN is connected, unless I had a connection already established to the Oracle database, I get an ORA, TNS:listener does not currently know of service requested in connect descriptor, but this appears to be because of the ORA TNS:permission denied error from the listener, which is the error I get if I run a "lsnrctl service" statement.

If I am not connected to the VPN, then the local machine connects to the Oracle databases without any errors, and all seems fine which seemed to be what you described. But then the machine is not attached to the network, so none of the other machines can connect to the Oracle databases. This is quite expected behavior. I am not aware of any workaround for this. You may try consulting MOS if they give you a solution to bypass this using some parameter etc.

I recently faced this error message while trying to connect with the database running on my local Windows host using a TNS service. Following is what I faced. Copyright c , , Oracle. All rights reserved. Used parameter files:. OK msec. Ace November 26, at AM. Check the images below, if you are on Windows try to adjust the values and restart the Windows listener service.

Then try to connect to database. Painfully I realized the truth that, there are NO straight forward solution to this error for the version in concern which is As I managed to start the instance successfully prior a restart, I tried to recollect the sequence of starting and stopping the Windows services. So, I got back to services panel and stopped the Oracle service, followed by restating the listener service. Stopped the Windows Service for Oracle database, waited couple of minutes and again tried to connect to the instance in the same CMD session.

Please make sure you try the upgrade using a virtual machine, spend some time analyzing logs and if you feel, it is worth taking a risk for the production, do the production patching using You may have to drop and recreate the Enterprise Manager repository if you are using it at all.

Updating the instance using Windows Service for Oracle Service is set as manual. After a reboot, I try to start the service manually. Few of them even claimed that they managed to start the Oracle service by turning off the firewall? Basically the 2nd page is purely for Linux, and if you are familiar with file permissions, easy to translate for Windows.

This issue could happen with any Oracle upgrade processes. So if you are that another unlucky one, please give the above hack a try.