This content has been marked as final. Show 6 replies
Did you change the port number or anything which has made your old TNS entry obsolete?
Normally, TNS-12535: TNS:operation timed out happens when you are blocked by firewall from accessing the database port from your client.
If this does not hold true in your case, you may want to check if all SQLNET adapters are fine (after the upgrade).
and check if TCP/IP is there.
If that's fine, check if you have exceeded the number of processes at database level.
select MAX_UTILIZATION, CURRENT_UTILIZATION, LIMIT_VALUE from v$resource_limit where
If nothing works, stop the listener, bounce the database and then restart the listener.
Unfortunately, none of the above worked (yes, even after a listener/database stop/restart).
I should have mentioned that there are 6 databases being hosted on this one machine, so wonder if that's got something to do with it?
I feel the tnsping result from another user is the problem - how can the service name not be shown? I'm guessing my tns/listener configuration must be wrong somehow, but I've no idea how.
Any ideas welcomed, I've hit a brick wall with this one.
post the following when you logged in as your user:
post the tnsnames.ora
Managed to solve the problem (with another pair of eyes) - it appears that the patch install had somehow changed the permissions of the tnsnames.ora file, thus denying read-access to anyone other than the oracle user.
Permissions altered, listeners stopped and started, and all's well.
Thanks to all of you who took the time to read/respond.
I am having same problem.
how and where did you given permission for the tnsnames.ora file..
Somehow the permissions on this file had changed so that only oracle could read them. I suspect it's something I did as opposed to the patch.
In my case I just needed to chmod gou+r tnsnames.ora. You'll find it in $ORACLE_HOME/network/admin
Hope this helps.