 | |
looking for blocking sql statement(s)
comp.databases.oracle.misc comp.databases.oracle.misc
 |
| | Thread Tools | Display Modes |
#31
 
| |||
| |||
|
Re: looking for blocking sql statement(s) -
02-15-2008
, 06:41 AM
|
You should be able to find a longer version of the SQL or the full sql by joining v$open_cursor to v$sqlarea (1000 bytes) or v$sqltext (multi- rows per SQL) or one of the other v$sql% views if it better suits your purpose. thank you very much, sometimes it is difficult too find a tree in a wood |
Quote:
|
HTH -- Mark D Powell -- Yes, it did |
--
wenn email, dann AndreasMosmann <bei> web <punkt> de
#32
| |||
| |||
|
|
You should be able to find a longer version of the SQL or the full sql by joining v$open_cursor to v$sqlarea (1000 bytes) or v$sqltext (multi- rows per SQL) or one of the other v$sql% views if it better suits your purpose. thank you very much, sometimes it is difficult too find a tree in a wood |
Quote:
|
HTH -- Mark D Powell -- Yes, it did |
--
wenn email, dann AndreasMosmann <bei> web <punkt> de
#33
| |||
| |||
|
|
You should be able to find a longer version of the SQL or the full sql by joining v$open_cursor to v$sqlarea (1000 bytes) or v$sqltext (multi- rows per SQL) or one of the other v$sql% views if it better suits your purpose. thank you very much, sometimes it is difficult too find a tree in a wood |
Quote:
|
HTH -- Mark D Powell -- Yes, it did |
--
wenn email, dann AndreasMosmann <bei> web <punkt> de
#34
| |||
| |||
|
|
Hi ng, we got a software that often causes any locks/deadlocks. We look for the reason for this and I found V$LOCK and V$SQL. The problem is, that I can find out SQL of the waiting sessions, but I can not find out the SQL statement(s) that caused the problem. Do you have any idea? Is it f.e. possible to log all sql statements used at the database (except of course the logging statement)? Hope anyone can help Andreas Mosmann -- wenn email, dann AndreasMosmann <bei> web <punkt> de |
#35
| |||
| |||
|
|
Hi ng, we got a software that often causes any locks/deadlocks. We look for the reason for this and I found V$LOCK and V$SQL. The problem is, that I can find out SQL of the waiting sessions, but I can not find out the SQL statement(s) that caused the problem. Do you have any idea? Is it f.e. possible to log all sql statements used at the database (except of course the logging statement)? Hope anyone can help Andreas Mosmann -- wenn email, dann AndreasMosmann <bei> web <punkt> de |
#36
| |||
| |||
|
|
Hi ng, we got a software that often causes any locks/deadlocks. We look for the reason for this and I found V$LOCK and V$SQL. The problem is, that I can find out SQL of the waiting sessions, but I can not find out the SQL statement(s) that caused the problem. Do you have any idea? Is it f.e. possible to log all sql statements used at the database (except of course the logging statement)? Hope anyone can help Andreas Mosmann -- wenn email, dann AndreasMosmann <bei> web <punkt> de |
#37
| |||
| |||
|
|
Hi ng, we got a software that often causes any locks/deadlocks. We look for the reason for this and I found V$LOCK and V$SQL. The problem is, that I can find out SQL of the waiting sessions, but I can not find out the SQL statement(s) that caused the problem. Do you have any idea? Is it f.e. possible to log all sql statements used at the database (except of course the logging statement)? Hope anyone can help Andreas Mosmann -- wenn email, dann AndreasMosmann <bei> web <punkt> de |
|
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.