| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
oemapp. You'll most likely want to run oemapp dbastudio, make sure that X is working first. | ||||||||
| Line: 24 to 24 | ||||||||
In sqlplus, set timing on gives elapsed time for sql commands. | ||||||||
| Changed: | ||||||||
| < < | -- TobyCabot - 23 May 2002 - 19 Jul 2002 | |||||||
| > > | In-doubt xactionsIf you end up with "in-doubt transactions" then you could be in a world of hurt since I've seen cases where they locked tables and hung around for days. You can't always force commits or rollbacks in OEM, so here's a recipe for getting rid of them when they happen (props to Kurt Stam): Log in as sys sysdba.select local_tran_id from dba_2pc_pending; rollback force ' local id from previous query '; This might not work; in that case you need to get a little more aggressive: If the server is in "auto undo mode" then you'll need to put it in manual mode (comment out the entries in the init.ora that put it in auto mode - manual is the default) and bounce it. Then connect as sys sysdba again and: execute dbms_transaction.purge_lost_db_entry( ' local id from previous query '); commit; (don't forget this!)
-- TobyCabot - 23 May 2002 - 08 Nov 2002 | |||||||