Please forward this error screen to carina. Please forward this error screen to alcona. M9 1a8 8 0 1 0 0 16A8 8 0 0 0 9 1zm. M9 1a8 8 toad for oracle patch key 1 0 0 16A8 8 0 0 0 9 1zM8 15.
I need to use PLSQL Developer to access oracle databases. I get the following error when I try to connect to my database. ORA-12154: TNS:could not resolve the connect identifier specified. I am able to use SQLPLUS from the command line to connect to the database, and tnsping returns successfully, but I can’t figure out why PLSQL Developer will not work – it’s using the right tnsnames. Anyone have an idea what I can do to fix this? I’ve looked at other threads about this specific error with no luck. I’m not talking about your computer’s domain.
DEFAULT_DOMAIN – do I need to give it a value? I’m not talking about the domain on the hostname either. I’ve been trying to troubleshoot this issue on a Windows 7 workstation along with the Network Engineers and the Oracle DBA at where I work. I have spent many times to find this solution! The parentheses caused this problem for me. After renaming the directory that housed my application to exclude the parentheses, it fixed it.
This error is very common, often the very first one you get on trying to establish a connection to your database. Check instance name has been entered correctly in tnsnames. There should be no control characters at the end of the instance or database name. If problem still persists, try to re-create TNS entry in tnsnames. As I can’t add a comment, just thought I’d post this for completion.
There is an existing networking bug where the networking layer is unable to parse program locations that contain parenthesis in the path to the executable which is attempting to connect to Oracle. Filed with Oracle, Bug 3807408 refers. This link gave me an idea connect to MS Access so i created a user in oracle sql developer and the tried to connect to it in Toad and it worked. For me it was bad formatting of the tnsnames. The indentation of the identifier string is required as shown in the tnsnames. Just wanted to add — apparently this can also be caused by installing Instant Client for 10, then realizing you want the full install and installing it again in a parallel directory. I don’t know why this broke it.