Toad is locking table in oracle
zino
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
shakespeare
"zino" <anton...@gmail.com> schreef in bericht
news:337a6229-e02d-4c04...@a39g2000pre.googlegroups.com...
Put Toad in read only query mode, or better: don't use Toad at all. It's
famous for locking tables.
Shakespeare
Walt
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
Shakespeare
"Walt" <walt_...@SHOESyahoo.com> schreef in bericht
news:13lrdhl...@corp.supernews.com...
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
Frank van Bortel
or use separate threads (will still lock - just
to indicate there's more than one option to look at)
Take a look at PL/SQL Developer of AllroundAutomations.
Better tool for developers (less obvious DBA stuff :) ),
better support for new Oracle versions, supports unicode
(ever seen russian job descriptions in the famous EMP table,
or chinese column names?!?).
And... it's a hell of a lot cheaper than TOAD! Current
prices: US$6k for an *unlimited* licence - TOAD will give
you about a single user license with no plugins for that!
--
Regards,
Frank van Bortel
Top-posting is one way to shut me up...
Walt
> "Walt" <walt_...@SHOESyahoo.com> schreef in bericht
>> 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.)
> But browsing a table and clicking on an entry in the result grid will....
> even if you don't edit at all.
Not that I have experienced. Oracle 10.2/W2k3, Toad 9.1, plus earlier
versions.
Looking at a table in the Schema Browser does not lock anything.
Clicking on a cel in the grid will not lock anything.
OTOH, changing the value of a cel in the grid *will* lock the record
(just like issuing an update without a commit), but as long as you
understand what it's doing it's not a problem.
Granted, the grid interface for tables in the Schema browser gives you
an easy way to update records - Just edit a cel and TOAD issues an
update, then click the button to commit or rollback. If this makes it
too easy and you wind up inadverdently issuing updates, find another
tool. I've never found it to be a problem.
TOAD is a sharp tool, and it'll allow you to be dangerous if you don't
understand it. Just like any useful tool. Don't give it to people who
can't use it properly.
BTW, Oracle's SQL Developer has a similar table grid interface, but it
doesn't issue any updates (or do any locking) until you commit. Perhaps
that's a better model, I'm agnostic - either is fine as long as you
understand what it's doing.
//Walt
shakespeare
"zino" <anton...@gmail.com> schreef in bericht
news:337a6229-e02d-4c04...@a39g2000pre.googlegroups.com...
You COULD use TOAD Security, a set of scripts creating tables in yoyr
database telling who can do what withToad on that database.
Shakespeare
shakespeare
"Frank van Bortel" <frank.va...@gmail.com> schreef in bericht
news:fjmr8g$vcn$1...@news5.zwoll1.ov.home.nl...
>>Take a look at PL/SQL Developer of AllroundAutomations.
My favorite too....
Shakespeare