You run oradebug from sqlplus.
SQL oradebug help
HELP [command] Describe one or all commands
SETMYPID Debug current process
SETOSPID ospid Set OS pid of process to debug
SETORAPID orapid ['force']Set
To disconnect the session use this :
Alter system disconnect session 'sid,serial#'
post_transaction;
--- Richard Ji [EMAIL PROTECTED] wrote:
You run oradebug from sqlplus.
SQL oradebug help
HELP [command] Describe
one or all commands
SETMYPID
shuan.tay\(PCI¾G¸R³Ô\),
Hi, It is because oracle will have to wake up pmon to rollback those
uncommitted transactions, so, the lock cannot be released befor the rollback complete.
You have to wake. Some trick said in this list is that you use
oradebug to wake up
This means the transaction issued by the session is
still rolling back. The session is not killed completely or the table locks
removed till the transaction completely rolls back.
So how do you know when it's going to be over? Just
issue the following query
SELECT USED_UBLK
FROM
chao_ping,
where to find the oradebug? is it a command?
what should i do to run the oradebug?
- Original Message -
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
Sent: Thursday, December 26, 2002 1:33 PM
shuan.tay\(PCI¾G¸R³Ô\),
Hi, It is because oracle will have to wake up
You don't mention the version of database.
It's not completely unheard of for a killed session holding
a lock to require a database bounce to release the lock, as
there are (unreproducable) cases of PMON never cleaning
up a session that was killed while holding a lock.
I've seen it happen a
