![]() | |
![]() |
| | Thread Tools | Search this Thread | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
We just got Toad 9.xxx. we noticed that every time an end user is working on a table (sinple select statement) from his end, the table will get locked and stay as, until this user's statement is finished or he close his session. Is that normal with oracle or is there something can be done on Toad side. thanks for help |
#3
| |||
| |||
|
|
shakespeare wrote: "zino" <antony6670 (AT) gmail (DOT) com> schreef in bericht news:337a6229-e02d-4c04-a592-c9d273d27666 (AT) a39g2000pre (DOT) googlegroups.com... We just got Toad 9.xxx. we noticed that every time an end user is working on a table (sinple select statement) from his end, the table will get locked and stay as, until this user's statement is finished or he close his session. Is that normal with oracle or is there something can be done on Toad side. thanks for help Put Toad in read only query mode, or better: don't use Toad at all. It's famous for locking tables. I've used TOAD for years, and never had a problem with locking tables. (Yeah, it'll lock tables if you issue a select for update, or update without committing, or do DDL, but that's all expected.) Something weird is going on. Not sure what, but out of the box there's no locking for a simple select. //Walt But browsing a table and clicking on an entry in the result grid will.... |
#4
| |||
| |||
|
|
"Walt" <walt_askier (AT) SHOESyahoo (DOT) com> schreef in bericht news:13lrdhlmnskdpef (AT) corp (DOT) supernews.com... shakespeare wrote: "zino" <antony6670 (AT) gmail (DOT) com> schreef in bericht news:337a6229-e02d-4c04-a592-c9d273d27666 (AT) a39g2000pre (DOT) googlegroups.com... We just got Toad 9.xxx. we noticed that every time an end user is working on a table (sinple select statement) from his end, the table will get locked and stay as, until this user's statement is finished or he close his session. Is that normal with oracle or is there something can be done on Toad side. thanks for help Put Toad in read only query mode, or better: don't use Toad at all. It's famous for locking tables. I've used TOAD for years, and never had a problem with locking tables. (Yeah, it'll lock tables if you issue a select for update, or update without committing, or do DDL, but that's all expected.) Something weird is going on. Not sure what, but out of the box there's no locking for a simple select. //Walt But browsing a table and clicking on an entry in the result grid will.... even if you don't edit at all. I have seen several customer sites where TOAD was absolutely forbidden for this behaviour. Sure, it's not the tool, but how you use it..... I used Toad for years without any complaints. It's the 'until this user's statement is finished' that worries me most.... Shakespeare Somewhere there's an option to use it read-only, |
),
#5
| |||
| |||
|
|
We just got Toad 9.xxx. we noticed that every time an end user is working on a table (sinple select statement) from his end, the table will get locked and stay as, until this user's statement is finished or he close his session. Is that normal with oracle or is there something can be done on Toad side. thanks for help |
#6
| |||
| |||
|
|
Take a look at PL/SQL Developer of AllroundAutomations. |
#7
| |||
| |||
|
|
I've used TOAD for years, and never had a problem with locking tables. |
![]() |
| Thread Tools | Search this Thread |
| Display Modes | |
| |