| about hang, waiting, lock [message #363130] |
Fri, 05 December 2008 03:02  |
kang
Messages: 89
Registered: November 2007
|
Member |
|
|
I don't the situtation exactly.
I did like this.
open plsql developer
and execute select * from some_table where key = 100 for update
and edit some rows,
and DIDN'T COMMIT or ROLLBACK;
PC was reset.(cause power failure)
reboot and reopen plsql develper.
and I can not update the row again.
-----------------------------------
of couse other coworkers do something else maybe.
I found the script to list locked session.
but I cannot find any.
after 2 hours later I can update the row.
I'm wondering what's happening and
want to know the concept of lock, waiting and hang etc.
TIA.
|
|
|
|
| Re: about hang, waiting, lock [message #364884 is a reply to message #363130] |
Wed, 10 December 2008 06:03  |
Frank Naude
Messages: 4581
Registered: April 1998
|
Senior Member |
|
|
|
Well, "for update" means you are locking the rows. No other session will be able to lock those rows until your session COMMITs, ROLLBACKs or gets killed. My guess is that your session was still active as the database didn't realized that your PC was rebooted. To shorten this period, try to play with the "sqlnet.expire_time" setting in your server's [[SQLNET.ORA]] file.
|
|
|
|
| Re: about hang, waiting, lock [message #364920 is a reply to message #363130] |
Wed, 10 December 2008 08:18 |
joy_division
Messages: 4963
Registered: February 2005
Location: East Coast USA
|
Senior Member |
|
|
You can kill your session by looking in V$SESSION. It's dangerous if you do not know what you are doing, so use caution. Search forALTER SYSTEM KILL SESSION... |
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
