SQL Window connecting rather than executing script

[BobbyH]

After I connect and run a select query I get "Could not logon as
ORA-02391: exceeded simultaneous SESSIONS_PER_USER limit

I disconnect/connect and try again - same thing.
Appears as if my connect is stored in memory and tries to connect rather than execute the sql.

Any ideas? Thanks!
Bobby

 

[rbrooker]

maybe there is a profile setting on the database for the user you are connecting as. you could also try running the app in "single session mode".

 

[BushPilot]

PL/SQL Developer uses one connection to connect and offer all the items in the browser etc. If you create a new SQL session/window in PL/SQL Developer, it does another database connection.
So if you open 4 new SQL session, you will have 5 database connections under that user. There is definitly a restriction on the database/profile, allowing you only one connection at any given time.

Speak to your DBA.

 

[Marco Kalter]

You can also switch to "Dual Session" mode (Tools > Preferences > Connection page). Now PL/SQL Developer will use one session for general DDL activities, and one for all SQL Windows, Test Windows, Command Windows, and so on.

This does of course not solve anything if you allowed just one session. In that case you can use "Single Session" mode, but this is very restricting.

 

[BobbyH]

Figured it was something to do with sessions but can't see where! Just moved from TOAD to this so still getting the hang of it!
Thanks guys, appreciated.