Database Issues.

[bob1212]

Seem to be having trouble with our developers locking records and having to re-boot, sometimes having to bring down the database to kill a session that won't release. This is happening against 9i, mostly on the Oracle 11i apps schema - DBAs want us to download Toad for a try ... since our Oracle contractors had no issuses and thats what they where using .. Any ideas?

We "launch " your product from a Novell Network and run against Solaris databases.
-- Could this be a configuration Issue. ?
Thanks - I want my PLSQL DEVELOPER ! -
(its a great product .. thanks.)

 

[Marco Kalter]

Record locks can only exist for the duration of a transaction or session. Therefore, if you disconnect PL/SQL Developer these locks should disappear. If this is not the case, then are you sure that these locks are related to PL/SQL Developer?

------------------
Marco Kalter
Allround Automations

 

[bob1212]

Thanks Marco - I had some mis-information in the first post - dbs is at 8.17 and at least once on a seperate schema in 8.16

I'll make sure that the developer re-boots instead of using task manager (win 2000) to end the task - the PL/SQL Developer app is 'busy ' the entire time - so you can't disconnect - it is locked also. If the reboot clears the database lock - then we'll have to consider the app as part of the problem.
Pretty sure it is not the code .. because the next day (or hour)the Delete or update statement works fine - 2 seconds ..etc

Also weird is the Dba 'kills' the locked session - which comes backed marked as killed - but just won't go away..

 

[Marco Kalter]

For updates through the SQL Window, PL/SQL Developer first checks for locks. How exactly do you cause these locks that lead to this situation?

------------------
Marco Kalter
Allround Automations

 

[bob1212]

M- I just watched someone lock up their App - It is only happening (98%) when opening a package and running it in a 'test' window.

The scenerio I just saw locked up the developer program when stepping through a package.. it stopped responding (locks)as a variable was being defined (xx.xx%type)- just got the hourglass - she says it works in test mode if you press the green Run button - but locks at different points if Stepping through the test. To me that seems as if a win2000/mem problem on her machine.
She can't debug wth it right now..
I'll have her try on my machine.. Database is fine (no locks at the moment).. I'll be back. Thanks.