ORA-12502: TNS:listener received no CONNECT_DATA from client

[Stew Stryker]

Ever since I upgraded to 9.0.0.1601 of PSD, I've started getting the above error when I either try to connect to the database or run the first query/update after connecting. The problem is that it's very sporadic. I haven't found an exact case when it always happens.

I had the new "Allow multiple connections" feature turned on, and I really liked it, but I think that's what's causing this error??? I was letting PSD store my login history with passwords, so I thought it should always have the complete connection information.

I've used the Reconnect Plug-In for years, but I thought maybe that's conflicting with the new Multiple Connections feature. But I still have the problem even after disabling the plug-in. (I haven't tried uninstalling it.)

If I turn off the "Allow multiple connections" feature and restart PSD, I still get the error if I try to log in from the initial login prompt. When I use the Session->Set Main Connection->Imported Fixed History (which includes passwords), it fails about 50% of the time.

Is anyone else seeing this problem?

Suggestions?

BTW, even after turning off "Allow multiple connections", the Session->Set Main Connection menu still displays, which I would expect to be turned off?

Thanks,

Stew

 

[Patrick Holmes]

I may be having a related problem. Using version 8.0.4, if login to a different database, then the session changes to the correct database. If using version 9, if login to a different database, the session is incorrectly still logged into the previous database! I've emailed support to report this bug.

 

[Marco Kalter]

Ever since I upgraded to 9.0.0.1601 of PSD, I've started getting the above error when I either try to connect to the database or run the first query/update after connecting. The problem is that it's very sporadic. I haven't found an exact case when it always happens.

The ORA-12502 error is very low-level. An application (like PL/SQL Developer) does not pass CONNECT_DATA, but passes a local service name which is internally translated to CONNECT_DATA by the Oracle Client. Can you review your tnsnames.ora file and veridy that all entries are correct?

 

[Marco Kalter]

I may be having a related problem. Using version 8.0.4, if login to a different database, then the session changes to the correct database. If using version 9, if login to a different database, the session is incorrectly still logged into the previous database! I've emailed support to report this bug.

Version 9.0 added support for multiple simultaneous connections, where each window or tool can have its own connection. If a Window is connected as user A, changing the PL/SQL Developer main (default) connection to user B will not affect this window. To change an individual Window connection, click on the connection name in the status bar of that Window and select a different connection or "Other".

To revert to 8.0 behavior, go to Tools > Preferences > Oracle / Connection and disable the "Allow multiple connections" option.

 

[Stew Stryker]

Marco,

Thanks for the quick and helpful support.

It looks like this was a local problem. I got the following response from one of our DBAs: "We made a 'tweak' to hopefully fix this problem."

I'm not getting this error at all since then.

Thanks also for clarifying the Main vs Window connection. I didn't have clear in my head until after I'd posted this the distinction between the connection in the application title bar vs at the bottom of a SQL window. I get it now from your comments as well as some pointed RTFM. Sorry I didn't try the latter first thing!

I'm still unclear on why changing the connection at the bottom of a code window sometimes shows an asterisk next to the name, and it doesn't actually connect until I click the asterisk. But I've gotten used to it.

Thanks again,

Stew