Deadlock trace analyze DID 0001-...
Please help me!
Does anybody knows that in an deadlock trace file what that means: "DID 0001-0017-000025CF"
Parts of sample file:
The following deadlock is not an ORACLE error. It is a
deadlock due to user error in the design of an application
or from issuing incorrect ad-hoc SQL. The following
information may aid in determining the deadlock:
Deadlock graph:
---------Blocker(s)-------- ---------Waiter(s)---------
Resource Name process session holds waits process session holds waits
TX-00060007-00049749 25 33 X 23 9 X
TX-0007000d-00037829 23 9 X 25 33 X
session 33: DID 0001-0019-000020EF* session 9: DID 0001-0017-000025CF
session 9: DID 0001-0017-000025CF session 33: DID 0001-0019-000020EF
Rows waited on:
Session 9: obj - rowid = 00013176 - AAATZSAAeAAAmSyAAH
I would like to know that is it an important fact, or not.
Thx,
Gyula
Hi,
SEssion 33 is blocking Session 9.
Object id = 1132910 - Object which is having blocking issue
select object_name from all_objects where object_id =1132910
TX is structured <rbs><slot><wrap>
TX-00060007-00049749 25 *33* X 23 9 X - blocking session
TX-0007000d-00037829 23 *9* X 25 33 X - blocked session
*25* - process *33* - blocker X - holds wait
*23* - process *9* - waiter X- same as above
as it does not have any row - might havig with some constraints issue on column level like unqiue constraints
Check that
HTH
- Pavan Kumar N
Similar Messages
-
Hi, I have 11.1.0.7. RAC Linux database. I can see 'Global Enqueue Services Deadlock detected. More info in file [file_name]' in alert file.
Is there any tool/steps to interpret content of this trace file? This trace file have different format comparing to 10g and it is difficult to understand what caused deadlock.
Any suggestions greatly appreciated.
M.Hi,
SEssion 33 is blocking Session 9.
Object id = 1132910 - Object which is having blocking issue
select object_name from all_objects where object_id =1132910
TX is structured <rbs><slot><wrap>
TX-00060007-00049749 25 *33* X 23 9 X - blocking session
TX-0007000d-00037829 23 *9* X 25 33 X - blocked session
*25* - process *33* - blocker X - holds wait
*23* - process *9* - waiter X- same as above
as it does not have any row - might havig with some constraints issue on column level like unqiue constraints
Check that
HTH
- Pavan Kumar N -
Get blocker from the (self) deadlock trace file
Hi,
Recently I had an issue on a 10.2.0.4 single instance database where deadlocks were occurring. The following test case reproduces the problem (I create three parent tables, one child table with indexed foreign keys to all three parent tables and a procedure which performs an insert into the child table in an autonomous transaction):
create table parent_1(id number primary key);
create table parent_2(id number primary key);
create table parent_3(id number primary key);
create table child( id_c number primary key,
id_p1 number,
id_p2 number,
id_p3 number,
constraint fk_id_p1 foreign key (id_p1) references parent_1(id),
constraint fk_id_p2 foreign key (id_p2) references parent_2(id),
constraint fk_id_p3 foreign key (id_p3) references parent_3(id)
create index i_id_p1 on child(id_p1);
create index i_id_p2 on child(id_p2);
create index i_id_p3 on child(id_p3);
create or replace procedure insert_into_child as
pragma autonomous_transaction;
begin
insert into child(id_c, id_p1, id_p2, id_p3) values(1,1,1,1);
commit;
end;
insert into parent_1 values(1);
insert into parent_2 values(1);
commit;And now the action that causes the deadlock:
SQL> insert into parent_3 values(1);
1 row created.
SQL> exec insert_into_child;
BEGIN insert_into_child; END;
ERROR at line 1:
ORA-00060: deadlock detected while waiting for resource
ORA-06512: at "SCOTT.INSERT_INTO_CHILD", line 4
ORA-06512: at line 1My question is: how can I determine which table the insert into CHILD was waiting on? It could be waiting on PARENT_1, PARENT_2, PARENT_3, a combination of them or even on CHILD if I tried to insert a duplicate primary key in CHILD. Since we have the full testcase we know that it was waiting on PARENT_3 (or better said, it was waiting for the "parent" transaction to perform a commit/rollback), but is it possible to determine that solely from the deadlock trace file? I'm asking that because to pinpoint the problem I had to perform redo log mining, pl/sql tracing with DBMS_TRACE and manual debugging on a clone of the production database which was restored to a SCN just before the deadlock occurred. So, I had to do quite a lot of work to get to the blocker table and if this information is already in the deadlock trace file, it would have saved me a lot of time.
Below is the deadlock trace file. From the "DML LOCK" part I guess that the child table (tab=227042) holds a mode 3 lock (SX), all the other three parent tables have mode 2 locks (SS), but from this extract I can't see that parent_3 (tab=227040) is blocking the insert into child:
Deadlock graph:
---------Blocker(s)-------- ---------Waiter(s)---------
Resource Name process session holds waits process session holds waits
TX-00070029-00749150 23 476 X 23 476 S
session 476: DID 0001-0017-00000003 session 476: DID 0001-0017-00000003
Rows waited on:
Session 476: obj - rowid = 000376E2 - AAA3biAAEAAA4BwAAA
(dictionary objn - 227042, file - 4, block - 229488, slot - 0)
Information on the OTHER waiting sessions:
End of information on OTHER waiting sessions.
Current SQL statement for this session:
INSERT INTO CHILD(ID_C, ID_P1, ID_P2, ID_P3) VALUES(1,1,1,1)
----- PL/SQL Call Stack -----
object line object
handle number name
3989eef50 4 procedure SCOTT.INSERT_INTO_CHILD
391f3d870 1 anonymous block
SO: 397691978, type: 36, owner: 39686af98, flag: INIT/-/-/0x00
DML LOCK: tab=227042 flg=11 chi=0
his[0]: mod=3 spn=35288
(enqueue) TM-000376E2-00000000 DID: 0001-0017-00000003
lv: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 res_flag: 0x6
res: 0x398341fe8, mode: SX, lock_flag: 0x0
own: 0x3980df420, sess: 0x3980df420, proc: 0x39859c660, prv: 0x398341ff8
SO: 397691878, type: 36, owner: 39686af98, flag: INIT/-/-/0x00
DML LOCK: tab=227040 flg=11 chi=0
his[0]: mod=2 spn=35288
(enqueue) TM-000376E0-00000000 DID: 0001-0017-00000003
lv: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 res_flag: 0x6
res: 0x3983386e8, mode: SS, lock_flag: 0x0
own: 0x3980df420, sess: 0x3980df420, proc: 0x39859c660, prv: 0x3983386f8
SO: 397691778, type: 36, owner: 39686af98, flag: INIT/-/-/0x00
DML LOCK: tab=227038 flg=11 chi=0
his[0]: mod=2 spn=35288
(enqueue) TM-000376DE-00000000 DID: 0001-0017-00000003
lv: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 res_flag: 0x6
res: 0x398340f58, mode: SS, lock_flag: 0x0
own: 0x3980df420, sess: 0x3980df420, proc: 0x39859c660, prv: 0x398340f68
SO: 397691678, type: 36, owner: 39686af98, flag: INIT/-/-/0x00
DML LOCK: tab=227036 flg=11 chi=0
his[0]: mod=2 spn=35288
(enqueue) TM-000376DC-00000000 DID: 0001-0017-00000003
lv: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 res_flag: 0x6
res: 0x39833f358, mode: SS, lock_flag: 0x0
own: 0x3980df420, sess: 0x3980df420, proc: 0x39859c660, prv: 0x39833f368
----------------------------------------Thank you in advance for any comments,
JureHi Jonathan,
thank you very much for your reply which more than answers my question. I think it actually clears a lot of doubts I had about TX locks, since your mentioning of "undo segment header transaction table" pointed me in the right direction for further research on this topic (honestly, I didn't know what's "behind" TX locks). So if I understood correctly, to determine which table is the blocker (in the testcase presented above), you have to have some kind of history of executed SQL statements (e.g. by mining redo logs)?
The statement you wrote:
At this point, and with your example, the waiting session is waiting on a TX (transaction) lock - this means it has not idea (and no interest) in the actual data involved, it is merely waiting for an undo segment header transaction table slot to clear. and the example with the savepoint you gave, made me think of some of the consequences of that behaviour. That is probably the reason why it is not possible to get the "blocker" table from v$lock (although sometimes it's possible to get it from v$session.row_wait_obj#) when a session tries to change a row another session holds in exclusive mode, e.g.:
create table t1 (id number);
insert into t1 values (1);
commit;
Session 126:
SID = 126> update t1 set id=2 where id=1;
1 row updated.
Session 146:
SID = 146> update t1 set id=2 where id=1;
{session hangs}
In a separate session:
SQL> SELECT CASE
2 WHEN TYPE = 'TM'
3 THEN (SELECT object_name
4 FROM user_objects
5 WHERE object_id = l.id1)
6 END object_name,
7 SID, TYPE, id1, id2, lmode, request, BLOCK
8 FROM v$lock l
9 WHERE SID IN (126, 146)
10 ORDER BY SID, TYPE, 1
11 /
OBJECT_NAME SID TY ID1 ID2 LMODE REQUEST BLOCK
T1 126 TM 68447 0 3 0 0
126 TX 262153 4669 6 0 1
T1 146 TM 68447 0 3 0 0
146 TX 262153 4669 0 6 0The only thing I can tell from this output is that session 146 is trying to get a TX lock in exclusive mode, and session 126 is blocking it, the reason of the blocking being unknown from this view alone.
Since I'd like to get a better understanding on the mechanics behind this (e.g. why the blocked session can't know the segment that is waiting for, since it has to go to the same segment's data block to find the address of the undo segment header transaction table slot? ; can we get the content/structure of the transaction table in the data block - probably by making a block dump?), do you have any source where a more in depth explanation what happens "behind the scenes" is available (perhaps in Oracle Core?)? Some time ago I found a link on your blog http://jonathanlewis.wordpress.com/2010/06/21/locks/ which points to Franck Pachot's article where he nicely explains the various locking modes: http://knol.google.com/k/oracle-table-lock-modes#. There I also found Kyle Hailey's presentation about locks http://www.perfvision.com/papers/09_enqueues.ppt where slide 23 nicely depicts what's going on when acquiring TX locks. Of course I'll try to search on my own, but any other source (especially from an authority like you) is more than welcome.
Thank you again and regards,
Jure -
Different Deadlock trace files
Hello,
In our application we use to have deadlock issues and i need to analyze that
trace file.Some time i use to have trace files which is having current session and
waiting session information and with modules and queries they are executing in top section
of trace file only , no need to read below data in trace file . But some times the
trace files are different..all update or select for update queries are spread
across the file and very difficult to understand which was locking what. Is that in rac or 11g environment
deadlock trace file is having different structure,?
One more question regarding deadlock ...many time we found that the current
query is updating on table A and waiting query updating on table B .. Is it possible
to have deadlock scenario when queries are working on different tables ? or
many be it is happening only if tables are in relation like parent and child ?hi,
Are you referring to .trm extention trace files which youare unable to read?
Here is good explanation of reading deadlock trace files
ORA-00060 Deadlock trace files.. how to read?
Thanks,
Ajay More
http://www.moreajays.com -
I have a short question regarding the trace analyzer... I downloaded this software from metalink 224270.1. When i tried to install the tool i ran into some 'ORA-00942: table or view does not exist'. The documentation told me that for rdbms 9.0x i must create this tablespace
create tablespace TRCA datafile '<some_path>trca01.dbf'
size 100M autoextend on next 100M permanent
default storage ( initial 1M next 1M)
extent management dictionary;
the problem is, i cant create this tablespace because my system tablespace is managed locally so i always run into
ERROR at line 1:
ORA-12913: Cannot create dictionary managed tablespace
The doc says : 'you need to install this TRCA tool on a dictionary managed tablespace' ...
is there a workaround? What would happen if i set up the tablespace locally managed?
regards
hanninalI was using trace_analyze in oracle9i and I was able to see all bind variables in the tracelog generated by trace_analyzer, now in Oracle10g, the binds didn't in the tracelog generated in trace_analyzer , Anyone can explain how can I got the binds in the trace level 12 using trace_analyzer?
-
Peculiar Behavior with trace flag 1204 and 1222 (deadlock traces)
I have noticed that any error using openquery whilst these trace flags are on will cause the sql server service to shut down.
If the trace flags are not running then we simply receive an error and the service will not shut down, any idea how we can prevent openquery errors from shutting the service down whilst we are monitoring for deadlocks using trace flags?
The log shows the following text "The MSSQLSERVER service terminated unexpectedly."
An example of code which will cause the above problem SELECT * FROM OPENQUERY(NONEXISTANTSERVER,'select * from dual')Hello,
Use extended events instead of those trace flags. Please read the following articles:
http://blogs.msdn.com/b/sqlserverfaq/archive/2013/04/27/an-in-depth-look-at-sql-server-memory-part-2.aspx
http://www.sql-server-performance.com/2012/capture-sql-server-deadlocks-extended-events/
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com
Hi yes this is what I did in the end, thanks -
hi,
after i run trcanlzr.sql , ibget the following error in the output file
Value passed to trcanlzr.sql:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
TRACE_FILENAME: C:\prod_ora_9811.trc
...analyzing C:\prod_ora_9811.trc
SELECT column_value FROM TABLE(trcanlzr.trca$g.tool_parameters)
ERROR at line 1:
ORA-00904: "TRCANLZR"."TRCA$G"."TOOL_PARAMETERS": invalid identifier
, how can i resolve this errorora-00904 = table or view does not exist..
-
Audit : to trace who did truncate of the table possible ?
Hi,
Yesterday some one has truncated the table data, any idea we can find out who did it? please see the configurations of my database.
BANNER
Oracle8i Enterprise Edition Release 8.1.7.4.0 - Production
PL/SQL Release 8.1.7.4.0 - Production
CORE 8.1.7.0.0 Production
TNS for HPUX: Version 8.1.7.4.0 - Production
NLSRTL Version 3.4.1.0.0 - Production
SQL> !uname -a
HP-UX db05 B.11.11 U 9000/800 1440856852 unlimited-user license
SQL> show parameter audit;
NAME TYPE VALUE
audit_file_dest string ?/rdbms/audit
audit_trail string NONE
transaction_auditing boolean TRUE
SQL>
-rw-r----- 1 oracle dba 2547 Aug 4 11:30 ora_26430.aud
-rw-r----- 1 oracle dba 4777 Aug 4 11:40 ora_1097.aud
-rw-r----- 1 oracle dba 3410 Aug 4 11:50 ora_8746.aud
-rw-r----- 1 oracle dba 2746 Aug 4 12:01 ora_14307.aud
-rw-r----- 1 oracle dba 2062 Aug 4 12:01 ora_14435.aud
-rw-r----- 1 oracle dba 4105 Aug 4 12:10 ora_18744.aud
-rw-r----- 1 oracle dba 2052 Aug 4 12:20 ora_23523.aud
-rw-r----- 1 oracle dba 4119 Aug 4 12:30 ora_28396.aud
-rw-r----- 1 oracle dba 3411 Aug 4 12:40 ora_3120.aud
-rw-r----- 1 oracle dba 3412 Aug 4 12:50 ora_9679.aud
-rw-r----- 1 oracle dba 2737 Aug 4 13:10 ora_22368.aud
-rw-r----- 1 oracle dba 1368 Aug 4 13:20 ora_28745.aud
-rw-r----- 1 oracle dba 4094 Aug 4 13:30 ora_3831.aud
-rw-r----- 1 oracle dba 4103 Aug 4 13:34 ora_6515.audNo, at this point because you did not have auditing turned on you cannot get the information desired. In my opinion you should configure all production databases to audit all DDL operations since you should create only once and reuse many times so auditing DDL should not generate much data.
The TRUNCATE command is a general exception to the above since for work/reporting tables I would espect that the table would be cleared out every time it is used but I would also expect the clearing user to be an application user which executes a stored procedure to perform the truncate and these are easy to filter out of any reports you run and to report on the use of the truncate procedure by any user other than the expected username.
If you set up auditing be sure to set up a purge at the same time.
IMHO -- Mark D Powell -- -
How to find username from trace file for deadlock due to user
This is the info from the trace file.
*** 2003-08-18 08:07:40.590
*** SESSION ID:(560.60728) 2003-08-18 08:07:40.560
DEADLOCK DETECTED
Current SQL statement for this session:
SELECT S.AVAILABLE,GET_AVAIL(S.PRODUCT_ID),S.ON_HAND,S.W_PL,S.PRODUCT_GROUP,S.SIZE_ID,S.COLOR_ID,S.ONEZ,S.COST,IS_IT_KIT(:b1),
NVL(PR.R_AVAIL,0),NVL(PR.R_SOLD,0),NVL(PR.UNIT_OF_MEASURE,'QTY'),NVL(DECODE(PR.AV_CT,0,1,PR.AV_CT),1) FROM ACNTV.SKU S,ACNTV
.PRERED_QUANTITIES PR WHERE S.PRODUCT_ID = PR.PRODUCT_ID (+) AND S.PRODUCT_ID = :b1 FOR UPDATE OF S.ON_HAND,
S.W_PL,PR.R_AVAIL
The following deadlock is not an ORACLE error. It is a
deadlock due to user error in the design of an application
or from issuing incorrect ad-hoc SQL. The following
information may aid in determining the deadlock:
Deadlock graph:
---------Blocker(s)-------- ---------Waiter(s)---------
Resource Name process session holds waits process session holds waits
TX-0021004b-000125d8 366 560 X 329 135 X
TX-0008003b-000125fc 329 135 X 366 560 X
session 560: DID 0001-016E-00000002 session 135: DID 0001-0149-00000002
session 135: DID 0001-0149-00000002 session 560: DID 0001-016E-00000002
Rows waited on:
Session 135: obj - rowid = 00017FAC - AAAX+sAAPAAAS9/AAP
Session 560: obj - rowid = 0001586C - AAAVhsABXAAAAIRAAN
We know the objects ,but how to find out the username ?
ThanksHi;
Please see:
How To Check If a Profile Option Is Set In Oracle Application [ID 470102.1]
How to list E-Business Suite Profile Option values for all levels using SQLPlus [ID 201945.1]
How to Search all of the Profile Options for a Specific Value [ID 282382.1]
Regard
Helios -
Deadlock occur how to read trace file session info
i got a dead lock & here is the part of trace from the call stack here i know one process but how i can get the inofrmation of
process 237 session 126 , i want to know which two process are involved in dead lock , i know table and rowid but i want to know the secod call stack or procedure if any one can help please reply .
*** 2010-08-16 17:32:48.038
*** SESSION ID:(126.255) 2010-08-16 17:32:47.880
DEADLOCK DETECTED ( ORA-00060 )
The following deadlock is not an ORACLE error. It is a
deadlock due to user error in the design of an application
or from issuing incorrect ad-hoc SQL. The following
information may aid in determining the deadlock:
Deadlock graph:
---------Blocker(s)-------- ---------Waiter(s)---------
Resource Name process session holds waits process session holds waits
TX-001a0026-0002969f 237 126 X 253 147 X
TX-00010014-00020a0a 253 147 X 237 126 X
session 126: DID 0001-00ED-00000028 session 147: DID 0001-00FD-000000A0
session 147: DID 0001-00FD-000000A0 session 126: DID 0001-00ED-00000028
Rows waited on:
Session 147: obj - rowid = 00001209 - AAAEiHAA0AAACCzABA
(dictionary objn - 4617, file - 52, block - 8371, slot - 64)
Session 126: obj - rowid = 00001209 - AAAEiHAA0AAACCyAAd
(dictionary objn - 4617, file - 52, block - 8370, slot - 29)
Information on the OTHER waiting sessions:
Session 147:
pid=253 serial=316 audsid=21499288 user: 77/<none>
O/S info: user: , term: , ospid: 1234, machine: reg-bpel1.viterra.ca
program:
client info: BPEL_MESSAGING 1.00 SHIPMENT_ACTUALS_SYNC MSG_INTF_BATCH
Current SQL Statement:
SELECT NEXT_ID, UPDATE_DT_TIME, UPDATE_USER_ID FROM ID_V WHERE UPPER(TABLE_NAME) = UPPER(:B1 ) FOR UPDATE OF NEXT_ID
End of information on OTHER waiting sessions.
Current SQL statement for this session:
SELECT NEXT_ID, UPDATE_DT_TIME, UPDATE_USER_ID FROM ID_V WHERE UPPER(TABLE_NAME) = UPPER(:B1 ) FOR UPDATE OF NEXT_ID
----- PL/SQL Call Stack -----
object line object
handle number name
373209A0 74 package body GA_APPLICATION.DATALESS_KEY_PROCESSING_PKG
373209A0 156 package body GA_APPLICATION.DATALESS_KEY_PROCESSING_PKG
407DC818 247 package body GA_APPLICATION.MESSAGE_AND_HISTORY_PKG
407DC818 358 package body GA_APPLICATION.MESSAGE_AND_HISTORY_PKG
41502DC8 9705 package body GA_APPLICATION.BPEL_ORDER_PKG
41502DC8 5520 package body GA_APPLICATION.BPEL_ORDER_PKG
416091D0 1286 package body MSG_INTF_APPLICATION.ORDER_PKG
42C2C638 1 anonymous block
===================================================
PROCESS STATE
Process global information:
process: 31853F30, call: 36FF8998, xact: 3471B720, curses: 31B53BD8, usrses: 31B53BD8
SO: 31853F30, type: 2, owner: 0, flag: INIT/-/-/0x00
(process) Oracle pid=237, calls cur/top: 36FF8998/36FF8930, flag: (0) -
int error: 0, call error: 0, sess error: 0, txn error 0
(post info) last post received: 0 0 4
last post received-location: kslpsr
last process to post me: 3181e400 1 6
last post sent: 0 0 16
last post sent-location: ksasnd
last process posted by me: 3181e400 1 6
(latch info) wait_event=0 bits=0
Process Group: DEFAULT, pseudo proc: 31B01F50
O/S info: user: , term: , ospid: 000700E6
OSD pid info: OSDI process pid: 000700E6, image: MINBNDS
SO: 350BD728, type: 8, owner: 31853F30, flag: INIT/-/-/0x00
(FOB) flags=2 fib ptr=33aa6d60 incno=0 pending i/o cnt=0
SO: 350C2A98, type: 8, owner: 31853F30, flag: INIT/-/-/0x00
(FOB) flags=2 fib ptr=33aa62f0 incno=0 pending i/o cnt=0
SO: 350C28B8, type: 8, owner: 31853F30, flag: INIT/-/-/0x00
(FOB) flags=2 fib ptr=33a9d0d0 incno=0 pending i/o cnt=0
SO: 350C25E8, type: 8, owner: 31853F30, flag: INIT/-/-/0x00
(FOB) flags=2 fib ptr=33aa7fa8 incno=0 pending i/o cnt=0
SO: 350C0EC0, type: 8, owner: 31853F30, flag: INIT/-/-/0x00
(FOB) flags=2 fib ptr=33aaa438 incno=0 pending i/o cnt=0
SO: 350BB0A0, type: 8, owner: 31853F30, flag: INIT/-/-/0x00
(FOB) flags=2 fib ptr=33aaa190 incno=0 pending i/o cnt=0
SO: 350BB028, type: 8, owner: 31853F30, flag: INIT/-/-/0x00
(FOB) flags=2 fib ptr=33aa2c28 incno=0 pending i/o cnt=0
SO: 350BAF38, type: 8, owner: 31853F30, flag: INIT/-/-/0x00
(FOB) flags=2 fib ptr=33a9db40 incno=0 pending i/o cnt=0
SO: 350E12A8, type: 8, owner: 31853F30, flag: INIT/-/-/0x00
(FOB) flags=2 fib ptr=33aa2990 incno=0 pending i/o cnt=0
SO: 350C8B88, type: 8, owner: 31853F30, flag: INIT/-/-/0x00
(FOB) flags=2 fib ptr=33aa07a8 incno=0 pending i/o cnt=0
SO: 350CB2D0, type: 8, owner: 31853F30, flag: INIT/-/-/0x00
(FOB) flags=2 fib ptr=33aa14b0 incno=0 pending i/o cnt=0
SO: 350CB258, type: 8, owner: 31853F30, flag: INIT/-/-/0x00
(FOB) flags=2 fib ptr=33aa50b8 incno=0 pending i/o cnt=0
SO: 350DA3F0, type: 8, owner: 31853F30, flag: INIT/-/-/0x00
(FOB) flags=2 fib ptr=33aac620 incno=0 pending i/o cnt=0
SO: 35146570, type: 8, owner: 31853F30, flag: INIT/-/-/0x00
(FOB) flags=2 fib ptr=33a9e858 incno=0 pending i/o cnt=0
SO: 3516B278, type: 8, owner: 31853F30, flag: INIT/-/-/0x00
(FOB) flags=2 fib ptr=33aa4b78 incno=0 pending i/o cnt=0
SO: 35110D50, type: 8, owner: 31853F30, flag: INIT/-/-/0x00
(FOB) flags=2 fib ptr=33aa4e10 incno=0 pending i/o cnt=0
SO: 3510E380, type: 8, owner: 31853F30, flag: INIT/-/-/0x00
(FOB) flags=2 fib ptr=33aa8240 incno=0 pending i/o cnt=0
SO: 35109CB8, type: 8, owner: 31853F30, flag: INIT/-/-/0x00
(FOB) flags=2 fib ptr=33aa19e0 incno=0 pending i/o cnt=0
SO: 35104030, type: 8, owner: 31853F30, flag: INIT/-/-/0x00
(FOB) flags=2 fib ptr=33aa48e0 incno=0 pending i/o cnt=0
SO: 350FFFB0, type: 8, owner: 31853F30, flag: INIT/-/-/0x00
(FOB) flags=2 fib ptr=33a9f7f8 incno=0 pending i/o cnt=0
SO: 350FCD70, type: 8, owner: 31853F30, flag: INIT/-/-/0x00
(FOB) flags=2 fib ptr=33aa3400 incno=0 pending i/o cnt=0
SO: 350EF0A8, type: 8, owner: 31853F30, flag: INIT/-/-/0x00
(FOB) flags=2 fib ptr=33aab918 incno=0 pending i/o cnt=0
SO: 350E4650, type: 8, owner: 31853F30, flag: INIT/-/-/0x00
(FOB) flags=2 fib ptr=33aa6058 incno=0 pending i/o cnt=0
SO: 350D7930, type: 8, owner: 31853F30, flag: INIT/-/-/0x00
(FOB) flags=2 fib ptr=33aa84e8 incno=0 pending i/o cnt=0
SO: 35109E20, type: 8, owner: 31853F30, flag: INIT/-/-/0x00
(FOB) flags=2 fib ptr=33aa8cb0 incno=0 pending i/o cnt=0
SO: 350D6A00, type: 8, owner: 31853F30, flag: INIT/-/-/0x00
(FOB) flags=2 fib ptr=33a9cba0 incno=0 pending i/o cnt=0
SO: 350FAE98, type: 8, owner: 31853F30, flag: INIT/-/-/0x00
(FOB) flags=2 fib ptr=33aa1218 incno=0 pending i/o cnt=0
SO: 350FA5F8, type: 8, owner: 31853F30, flag: INIT/-/-/0x00
(FOB) flags=2 fib ptr=33a9f560 incno=0 pending i/o cnt=0
SO: 350FA238, type: 8, owner: 31853F30, flag: INIT/-/-/0x00
(FOB) flags=2 fib ptr=33a9d8a8 incno=0 pending i/o cnt=0
SO: 350EDAE8, type: 8, owner: 31853F30, flag: INIT/-/-/0x00
(FOB) flags=2 fib ptr=33a9c3c8 incno=0 pending i/o cnt=0
SO: 350EBF58, type: 8, owner: 31853F30, flag: INIT/-/-/0x00
(FOB) flags=2 fib ptr=33aab140 incno=0 pending i/o cnt=0
SO: 350EBD00, type: 8, owner: 31853F30, flag: INIT/-/-/0x00
(FOB) flags=2 fib ptr=33aacb50 incno=0 pending i/o cnt=0
SO: 350EBC88, type: 8, owner: 31853F30, flag: INIT/-/-/0x00
(FOB) flags=2 fib ptr=33aa21b8 incno=0 pending i/o cnt=0
SO: 350EBC10, type: 8, owner: 31853F30, flag: INIT/-/-/0x00
(FOB) flags=2 fib ptr=33aaaea8 incno=0 pending i/o cnt=0
SO: 350D0238, type: 8, owner: 31853F30, flag: INIT/-/-/0x00
(FOB) flags=2 fib ptr=33aac388 incno=0 pending i/o cnt=0
SO: 350CDF70, type: 8, owner: 31853F30, flag: INIT/-/-/0x00
(FOB) flags=2 fib ptr=33aabbb0 incno=0 pending i/o cnt=0
SO: 350CDEF8, type: 8, owner: 31853F30, flag: INIT/-/-/0x00
(FOB) flags=2 fib ptr=33aa1748 incno=0 pending i/o cnt=0
SO: 350CDE80, type: 8, owner: 31853F30, flag: INIT/-/-/0x00
(FOB) flags=2 fib ptr=33aa72a0 incno=0 pending i/o cnt=0
SO: 350CDE08, type: 8, owner: 31853F30, flag: INIT/-/-/0x00
(FOB) flags=2 fib ptr=33aa7538 incno=0 pending i/o cnt=0
SO: 350CDD90, type: 8, owner: 31853F30, flag: INIT/-/-/0x00
(FOB) flags=2 fib ptr=33aa6ac8 incno=0 pending i/o cnt=0
SO: 350CDD18, type: 8, owner: 31853F30, flag: INIT/-/-/0x00
(FOB) flags=2 fib ptr=33a9fd38 incno=0 pending i/o cnt=0
SO: 350CDB38, type: 8, owner: 31853F30, flag: INIT/-/-/0x00
(FOB) flags=2 fib ptr=33aa0a40 incno=0 pending i/o cnt=0
SO: 350CBEB8, type: 8, owner: 31853F30, flag: INIT/-/-/0x00
(FOB) flags=2 fib ptr=33aabe48 incno=0 pending i/o cnt=0
SO: 350CBA08, type: 8, owner: 31853F30, flag: INIT/-/-/0x00
(FOB) flags=2 fib ptr=33a9e080 incno=0 pending i/o cnt=0
SO: 350CB828, type: 8, owner: 31853F30, flag: INIT/-/-/0x00
(FOB) flags=2 fib ptr=33aa5350 incno=0 pending i/o cnt=0
SO: 350CB168, type: 8, owner: 31853F30, flag: INIT/-/-/0x00
(FOB) flags=2 fib ptr=33aa4108 incno=0 pending i/o cnt=0
SO: 350CB078, type: 8, owner: 31853F30, flag: INIT/-/-/0x00
(FOB) flags=2 fib ptr=33aa9720 incno=0 pending i/o cnt=0
SO: 350CB000, type: 8, owner: 31853F30, flag: INIT/-/-/0x00
(FOB) flags=2 fib ptr=33a9ce38 incno=0 pending i/o cnt=0
SO: 31B53BD8, type: 4, owner: 31853F30, flag: INIT/-/-/0x00
(session) trans: 3471B720, creator: 31853F30, flag: (100045) USR/- BSY/-/-/-/-/-
DID: 0001-00ED-00000028, short-term DID: 0000-0000-00000000
txn branch: 0
oct: 3, prv: 0, sql: 3731E1A8, psql: 3731E1A8, user: 77/<none>
O/S info: user: , term: , ospid: 1234, machine: reg-bpel1.viterra.ca
program:
client info: BPEL_Messaging 1.00 SO_SYNC MSG_INTF_BATCH
last wait for 'enqueue' blocking sess=0x31b60208 seq=11337 wait_time=3333245
name|mode=e3e70006, id1=10014, id2=20a0a
temporary object counter: 0
SO: 36D06490, type: 52, owner: 31B53BD8, flag: INIT/-/-/0x00
LIBRARY OBJECT PIN: pin=36d06490 handle=3731f318 mode=S lock=53af8dc8
user=31b53bd8 session=31b53bd8 count=1 mask=0041 savepoint=63373 flags=[00]
SO: 4C1AEF38, type: 51, owner: 31B53BD8, flag: INIT/-/-/0x00
LIBRARY OBJECT LOCK: lock=4c1aef38 handle=3eb115d8 mode=N
call pin=0 session pin=439995E8
htl=4C1AEF74[3403195C,510B35B8] htb=510B35B8
user=31b53bd8 session=31b53bd8 count=1 flags=[00] savepoint=63228
LIBRARY OBJECT HANDLE: handle=3eb115d8
namespace=CRSR flags=RON/KGHP/PN0/[10010000]
kkkk-dddd-llll=0000-0041-0041 lock=N pin=0 latch#=2
lwt=3EB115F0[3EB115F0,3EB115F0] ltm=3EB115F8[3EB115F8,3EB115F8]
pwt=3EB11608[3EB11608,3EB11608] ptm=3EB11660[3EB11660,3EB11660]
ref=3EB115E0[3EB11820, 3EB11820] lnd=3EB1166C[3EB1166C,3EB1166C]
LIBRARY OBJECT: object=3eb10850
type=CRSR flags=EXS[0001] pflags= [00] status=VALD load=0
DEPENDENCIES: count=6 size=16
AUTHORIZATIONS: count=1 size=16 minimum entrysize=28
ACCESSES: count=2 size=16
TRANSLATIONS: count=2 size=16
DATA BLOCKS:
data# heap pointer status pins change
0 3eb10a60 3eb10608 I/P/A 0 NONE
6 3eb108f8 3eb0f3a8 I/-/A 0 NONE
SO: 4C1AF910, type: 51, owner: 31B53BD8, flag: INIT/-/-/0x00
LIBRARY OBJECT LOCK: lock=4c1af910 handle=3eb1e3b8 mode=N
call pin=46E24C60 session pin=0
htl=4C1AF94C[3502B6B4,510B3680] htb=510B3680
user=31b53bd8 session=31b53bd8 count=1 flags=[00] savepoint=63227
LIBRARY OBJECT HANDLE: handle=3eb1e3b8
name=
INSERT INTO PO_MSG ( PO_MSG_ID ,PO_ID ,PO_NBR ,PO_DT ,LOC_ACCT_ID ,PO_FORMAT ,DS_ID ,QGRD_TABLE_PROD_ID ,TRANS_MODE ,TRA
NS_TYPE_ID ,SPLIT_WHEN ,LEAD_CAR_NBR ,PO_STATUS ,ENABLE_EXTEND_AMT ,CONTROL_NBR ,SHIP_WHEN ,PO_TYPE ,PRINT_COPIES ,PRINT
PRICE ,GENERATESO ,RETURN_AUTHORIZE ,ASSESS_STATE_ID ,REPEAT_ORDER ,REPEAT_NBR_DAYS ,REPEAT_DAY ,REPEAT_DAYS ,REPEAT_U
NTIL_DT ,CURRENCY_ID ,CURR_RATE_TYPE_ID ,EXCH_RATE_AVG ,COMMENTS_EXIST ,CREATE_USER_ID ,CREATE_DT_TIME ,UPDATE_USER_ID ,
UPDATE_DT_TIME ,REPEAT_TRIGGER ,
hash=e58fc51 timestamp=08-15-2010 08:22:27
namespace=CRSR flags=RON/KGHP/TIM/PN0/[10010000]
kkkk-dddd-llll=0000-0001-0001 lock=N pin=0 latch#=2
lwt=3EB1E3D0[3EB1E3D0,3EB1E3D0] ltm=3EB1E3D8[3EB1E3D8,3EB1E3D8]
pwt=3EB1E3E8[3EB1E3E8,3EB1E3E8] ptm=3EB1E440[3EB1E440,3EB1E440]
ref=3EB1E3C0[3EB1E3C0, 3EB1E3C0] lnd=3EB1E44C[3EAECA24,3EB20044]
LIBRARY OBJECT: object=3eb118f0
type=CRSR flags=EXS[0001] pflags= [00] status=VALD load=0
CHILDREN: size=16
child# table reference handle
0 3eb11a98 3eb11820 3eb115d8
DATA BLOCKS:
data# heap pointer status pins change
0 3eb25b40 3eb11980 I/P/A 0 NONE
SO: 4C752940, type: 51, owner: 31B53BD8, flag: INIT/-/-/0x00
LIBRARY OBJECT LOCK: lock=4c752940 handle=3eb20cf8 mode=N
call pin=3B503AF8 session pin=0
htl=4C75297C[36856DD4,510B3628] htb=510B3628
user=31b53bd8 session=31b53bd8 count=2 flags=[00] savepoint=63218
LIBRARY OBJECT HANDLE: handle=3eb20cf8
name=GA_APPLICATION.PO_AUR
hash=92b14a46 timestamp=06-29-2010 21:08:46
namespace=TRGR flags=KGHP/TIM/SML/[02000000]
kkkk-dddd-llll=0000-0059-0059 lock=N pin=0 latch#=5
lwt=3EB20D10[3EB20D10,3EB20D10] ltm=3EB20D18[3EB20D18,3EB20D18]
pwt=3EB20D28[3EB20D28,3EB20D28] ptm=3EB20D80[3EB20D80,3EB20D80]
ref=3EB20D00[3EB20D00, 3EB20D00] lnd=3EB20D8C[3EAB046C,3EB79DFC]
LIBRARY OBJECT: object=3eb20c10
type=TRGR flags=EXS/LOC[0005] pflags=NST [01] status=VALD load=0
DEPENDENCIES: count=17 size=32
READ ONLY DEPENDENCIES: count=2 size=16
ACCESSES: count=5 size=16
DATA BLOCKS:
data# heap pointer status pins change
0 3eb25ba8 3eb208f0 I/-/A 0 NONE
3 3eb207d0 0 -/P/- 0 NONE
4 3eb20838 3eb1f558 I/-/A 0 NONE
6 3eb208a0 3eb1dd60 I/-/A 0 NONE
----------------------------------------Hi,
---------Blocker(s)-------- ---------Waiter(s)---------
Resource Name process session holds waits process session holds waits
TX-001a0026-0002969f 237 *126* X 253 *147* X
TX-00010014-00020a0a 253 *147* X 237 *126* X
session 126: DID 0001-00ED-00000028 session 147: DID 0001-00FD-000000A0
session 147: DID 0001-00FD-000000A0 session 126: DID 0001-00ED-00000028
Rows waited on:
Session 147: obj - rowid = 00001209 - AAAEiHAA0AAACCzABA
*(dictionary objn - 4617, file - 52, block - 8371, slot - 64)*
Session 126: obj - rowid = 00001209 - AAAEiHAA0AAACCyAAd
*(dictionary objn - 4617, file - 52, block - 8370, slot - 29)*
Information on the OTHER waiting sessions:
Session 147:
pid=253 serial=316 audsid=21499288 user: 77/<none>
O/S info: user: , term: , ospid: 1234, machine: reg-bpel1.viterra.ca
program:
client info: BPEL_MESSAGING 1.00 SHIPMENT_ACTUALS_SYNC MSG_INTF_BATCH
Current SQL Statement:
SELECT NEXT_ID, UPDATE_DT_TIME, UPDATE_USER_ID FROM ID_V WHERE UPPER(TABLE_NAME) = UPPER(:B1 ) FOR UPDATE OF NEXT_ID
End of information on OTHER waiting sessions.
Current SQL statement for this session:
SELECT NEXT_ID, UPDATE_DT_TIME, UPDATE_USER_ID FROM ID_V WHERE UPPER(TABLE_NAME) = UPPER(:B1 ) FOR UPDATE OF NEXT_ID
Has most of the information.
You have to check what session 126 and 147 were doing. It also gives you information on object_id and rowid where you had the lock by two sessions.
The culprit is FOR UPDATE OF NEXT_ID.
Regards
Edited by: skvaish1 on Aug 18, 2010 5:26 PM -
Hi,
I've gotten a bunch of deadlocks in 8.1.7 and I'd like to be able to make use of the trace files, but the files are really cryptic and I can't find any documentation anywhere that explains how to read them. Moreover, I can't find any software that knows how to process them into something useful (tkprof just gives a basically empty file in return).
Anyone have any ideas?
TIAHi
My current application (still under development) is experiencing Oracle
deadlock problems.
The application is written using VB thru ADO and COM, Oracle 816.
My problem is that, while I can review the trace file produced, I can't
figure out what the actual deadlock is occurring on. I have seen deadlock
trace files that clearly state "table blah", but in this case, I get:
*** 2003-06-21 14:32:03.841
*** SESSION ID:(27.31211) 2003-06-21 14:32:03.810
DEADLOCK DETECTED
Deadlock graph:
---------Blocker(s)--------
Resource Name process session holds waits process session holds
waits
DX-0000003b-00000000 22 18 X 24 27
X
session 18: DID 0001-0018-0000003C session 27: DID
0001-0018-0000003C
Rows waited on:
Session 27: no row
*** 2001-06-21 14:32:03.857
ksedmp: internal or fatal error
ORA-00060: deadlock detected while waiting for resource
Is there something like TKPROF that will process the trace file and give
me
more info on what is happening? It looks like I am waiting for a resource
to be freed, but which one is the question.
thanks for any help. -
Deadlock : objn in trace indicates index
Hi All,
There was a deadlock detected and logged and I am trying to figure out the application issue that caused it.
Version info:
Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bi
PL/SQL Release 10.2.0.3.0 - Production
CORE 10.2.0.3.0 Production
TNS for HPUX: Version 10.2.0.3.0 - Production
NLSRTL Version 10.2.0.3.0 - ProductionHere is a snippet from the trace file:
Deadlock graph:
---------Blocker(s)-------- ---------Waiter(s)---------
Resource Name process session holds waits process session holds waits
TX-0016001f-00013ae8 68 892 X 229 818 S
TX-0007001c-0002c66a 229 818 X 101 929 S
TX-0010001d-000299c5 101 929 X 68 892 S
session 892: DID 0001-0044-00002E42 session 818: DID 0001-00E5-000003FD
session 818: DID 0001-00E5-000003FD session 929: DID 0001-0065-00001940
session 929: DID 0001-0065-00001940 session 892: DID 0001-0044-00002E42
Rows waited on:
Session 818: obj - rowid = 0003E8F1 - AAA+jxAEhAAAFeaAAA
(dictionary objn - 256241, file - 289, block - 22426, slot - 0)
Session 929: obj - rowid = 0003E8F1 - AAA+jxAEgAAAAFnAAA
(dictionary objn - 256241, file - 288, block - 359, slot - 0)
Session 892: obj - rowid = 0003E8F1 - AAA+jxAEgAAADIEAAAFrom the SQL listed, I see that the same update is being run by the 3 sessions.
UPDATE my_table
SET col1 = TRIM (NVL (:b5, '5')),
col2 = DECODE (NVL (:b5, '5'), '1', 1, '0', 1, '4', 1, 0),
col3 = :b4
WHERE col4 = :b3 AND col5 = :b2 AND col6 = :b1;The predicates have bind variables in them. If the bind variable is set to the same value, then I would expect this issue to occur. In this case I would expect the "objn - 256241" to point to table "my_table". However, when I lookup this in dba_objects, it points to the PK index for this table:
xxxx> select object_type
2 from dba_objects
3 where object_id = 256241;
OBJECT_TYPE
INDEXThe questions i have are:
1. Is my assumption correct
In this case I would expect the "objn - 256241" to point to table "my_table"2. I was going to use the rowids to check what row this is occuring on. How do I do this if I only have rowids from the index instead of the table? Is there another way to get the bind variable info from the deadlock trace file?
3. Any other suggestions about looking into this.
Thanks,
RahulDilip,
Sorry I missed the index info details.
It is a B-tree index. I am translating the table/index/column names from original in this post. Going by that the index would look something like this:
CREATE UNIQUE INDEX my_index ON my_table
col4 ASC, --corresponds to predicate in update stmt
col6 ASC,
col5 ASC, --corresponds to predicate in update stmt
col7 ASC,
col8 ASC,
col9 ASC
/Thanks,
Rahul -
Why when Oracle gives me a 00060 Deadlock error do my trace logs no graphs?
Normally everything you read online shows you that Oracle's trace files will contain a deadlock graph.
At work we have trace files being generated and when we look at the trace file reference by the alert file
there is no deadlock graph for any deadlock 00060 detected error.
We have an Oracle 11gR1 RAC cluster
Any idea why we wouldn't see deadlock graphs with all the useful information necessary to hunt down these deadlocks?Hi,
Actually word "Graph" was misleading, if you expect the graph you mention through tat link, then you are right, you should see that "graph. See the trace file name in the alert log file and then open that file and you should see this graph in the start of this trace file.
I created a deadlock scenario and following is what i find in my trace file which tells me session, object id and row ids involved in the dead lock.
{code}
DEADLOCK DETECTED
[Transaction Deadlock]
Current SQL statement for this session:
delete from test where ename='MILLER'
The following deadlock is not an ORACLE error. It is a
deadlock due to user error in the design of an application
or from issuing incorrect ad-hoc SQL. The following
information may aid in determining the deadlock:
Deadlock graph:
---------Blocker(s)-------- ---------Waiter(s)---------
Resource Name process session holds waits process session holds waits
TX-00030013-00006a5a 16 120 X 20 131 X
TX-0006000d-00006aff 20 131 X 16 120 X
session 120: DID 0001-0010-000001F5 session 131: DID 0001-0014-000000E2
session 131: DID 0001-0014-000000E2 session 120: DID 0001-0010-000001F5
Rows waited on:
Session 131: obj - rowid = 0001727B - AAAXJ7AAEAAAB8EAAH
(dictionary objn - 94843, file - 4, block - 7940, slot - 7)
Session 120: obj - rowid = 0001727B - AAAXJ7AAEAAAB8EAAN
(dictionary objn - 94843, file - 4, block - 7940, slot - 13)
Information on the OTHER waiting sessions:
Session 131:
pid=20 serial=594 audsid=189998 user: 54/SCOTT
O/S info: user: Salman, term: SALMAN, ospid: 6504:8036, machine: UTAC\SALMAN
program: sqlplus.exe
application name: SQL*Plus, hash value=3669949024
Current SQL Statement:
delete from test where ename='SCOTT'
End of information on OTHER waiting sessions.
{code}
*Note:* Please always write your code/output enclosed in {code} tag and see "Preview" before posting your reply
Thanks
Salman -
Hello,
I am beginner in oracle and i need to analyze the trace file, i have traced a session and converted the raw trace file into txt and html file using trace analyzer ,but after that how can i read or identyify which one produces a problem.
Please anyone suggest me .
Thanks in advance
NityaPl post your question in the appropriate database forum at http://forums.oracle.com/forums/category.jspa?categoryID=18
HTH
Srini -
ORA-00060 DEADLOCK DETECTED - Need Help
Hi Gurus,
I have a question on how to determine the trace log. Where the deadlock happen.
Please help. I have no other hint on how to resolve the error.
*** ACTION NAME:() 2008-08-06 03:34:21.740
*** MODULE NAME:(OEM.SystemPool) 2008-08-06 03:34:21.740
*** SERVICE NAME:(celcomdb) 2008-08-06 03:34:21.740
*** CLIENT ID:() 2008-08-06 03:34:21.740
*** SESSION ID:(113.3188) 2008-08-06 03:34:21.740
DEADLOCK DETECTED ( ORA-00060 )
[Transaction Deadlock]
The following deadlock is not an ORACLE error. It is a
deadlock due to user error in the design of an application
or from issuing incorrect ad-hoc SQL. The following
information may aid in determining the deadlock:
Deadlock graph:
---------Blocker(s)-------- ---------Waiter(s)---------
Resource Name process session holds waits process session holds waits
TM-0000c45a-00000000 119 113 X 27 60 SX
TX-0004002c-000269bc 27 60 X 119 113 X
session 113: DID 0001-0077-00000028 session 60: DID 0001-001B-00000278
session 60: DID 0001-001B-00000278 session 113: DID 0001-0077-00000028
Rows waited on:
Session 60: no row
Session 113: obj - rowid = 0000C384 - AAAMOEAADAAAF99AAA
(dictionary objn - 50052, file - 3, block - 24445, slot - 0)
Information on the OTHER waiting sessions:
Session 60:
pid=27 serial=1313 audsid=0 user: 51/SYSMAN
O/S info: user: oracle10, term: UNKNOWN, ospid: 14610456, machine: S63KLJ01
program: oracle@S63KLJ01 (J000)
application name: EM_PING, hash value=2147830874
action name: AGENT_STATUS_MARKER, hash value=2850782869
Current SQL information unavailable
End of information on OTHER waiting sessions.
Current SQL statement for this session:
UPDATE MGMT_OMS_PARAMETERS SET VALUE=TO_CHAR(SYSDATE, 'DD-Mon-YYYY HH24:MI:SS') WHERE HOST_URL=:B1 AND NAME='TIMESTAMP'
----- PL/SQL Call Stack -----
object line object
handle number name
70000006e5ab778 39 package body SYSMAN.MGMT_FAILOVER
70000002e8aaf98 1 anonymous block
===================================================
PROCESS STATE
Process global information:
process: 70000006f4b1598, call: 70000006a9c9320, xact: 70000006dedcf98, curses: 70000006f5a5a50, usrses: 70000006f5a5a50
SO: 70000006f4b1598, type: 2, owner: 0, flag: INIT/-/-/0x00
(process) Oracle pid=119, calls cur/top: 70000006a9c9320/70000006abfcaf8, flag: (0) -
int error: 0, call error: 0, sess error: 0, txn error 0
(post info) last post received: 0 0 9
last post received-location: ksqrcl
last process to post me: 70000006f484118 141 0
last post sent: 0 0 0
last post sent-location: No post
last process posted by me: none
(latch info) wait_event=0 bits=0
Process Group: DEFAULT, pseudo proc: 70000006f50bcd0
O/S info: user: oracle10, term: UNKNOWN, ospid: 11538508
OSD pid info: Unix process pid: 11538508, image: oraclecelcomdb@S63KLJ01
Dump of memory from 0x070000006F45FCD0 to 0x070000006F45FED8
70000006F45FCD0 00000004 00000000 07000000 6A9ABD00 [............j...]
70000006F45FCE0 00000010 0003139D 07000000 6ABFCAF8 [............j...]
70000006F45FCF0 00000003 0003139D 07000000 6F8FD600 [............o...]
70000006F45FD00 0000000B 0003139D 07000000 6F5A5A50 [............oZZP]
70000006F45FD10 00000004 00031291 00000000 00000000 [................]
70000006F45FD20 00000000 00000000 00000000 00000000 [................]
Repeat 26 times
70000006F45FED0 00000000 00000000 [........]
SO: 70000006f5a5a50, type: 4, owner: 70000006f4b1598, flag: INIT/-/-/0x00
(session) sid: 113 trans: 70000006dedcf98, creator: 70000006f4b1598, flag: (41) USR/- BSY/-/-/-/-/-
DID: 0001-0077-00000028, short-term DID: 0000-0000-00000000
txn branch: 0
oct: 6, prv: 0, sql: 70000006e5a9140, psql: 70000006e5a9410, user: 51/SYSMAN
O/S info: user: oracle10, term: unknown, ospid: 1234, machine: S63KLJ01
program: OMS
client info: S63KLJ01_Management_Service
application name: OEM.SystemPool, hash value=2960518376
last wait for 'enq: TX - row lock contention' blocking sess=0x70000006f5611e0 seq=322 wait_time=2929700 seconds since wait started=4
name|mode=54580006, usn<<16 | slot=4002c, sequence=269bc
Dumping Session Wait History
for 'enq: TX - row lock contention' count=1 wait_time=2929700
name|mode=54580006, usn<<16 | slot=4002c, sequence=269bc
for 'enq: TM - contention' count=1 wait_time=224489
name|mode=544d0006, object #=c45a, table/partition=0
for 'enq: TM - contention' count=1 wait_time=2929708
name|mode=544d0006, object #=c45a, table/partition=0
for 'SQL*Net message from client' count=1 wait_time=35033
driver id=28444553, #bytes=1, =0
for 'SQL*Net message to client' count=1 wait_time=1
driver id=28444553, #bytes=1, =0
for 'SQL*Net message from client' count=1 wait_time=227
driver id=28444553, #bytes=1, =0
for 'SQL*Net message to client' count=1 wait_time=1
driver id=28444553, #bytes=1, =0
for 'latch: library cache' count=1 wait_time=96826
address=70000006cf2f298, number=d6, tries=0
for 'latch: library cache' count=1 wait_time=36929
address=70000006cf2f0b8, number=d6, tries=0
for 'SQL*Net message from client' count=1 wait_time=131974
driver id=28444553, #bytes=1, =0
temporary object counter: 0
Virtual Thread:
kgskvt: 70000006e82cd98, sess: 70000006f5a5a50, vc: 0, proc: 70000006f4b1598
consumer group cur: OTHER_GROUPS (upd? 0), mapped: DEFAULT_CONSUMER_GROUP, orig:
vt_state: 0x200, vt_flags: 0x30, blkrun: 0
is_assigned: 1, in_sched: 0 (0)
vt_active: 0 (pending: 1)
used quanta: 0 (cg: 0)
cpu start time: 0, quantum status: 0x0
quantum checks to skip: 0, check thresh: 0
idle time: 0, active time: 0 (cg: 0)
cpu yields: 0 (cg: 0), waits: 0 (cg: 0), wait time: 0 (cg: 0)
queued time outs: 0, time: 0 (cur 0, cg 0)
calls aborted: 0, num est exec limit hit: 0
undo current: 0k max: 0k
UOL used : 0 locks(used=2, free=0)
KGX Atomic Operation Log 70000002eb54978
Mutex 0(0, 0) idn 0 oper NONE
Cursor Parent uid 113 efd 15 whr 22 slp 0
oper=NONE pt1=0 pt2=0 pt3=0
pt4=0 u41=0 stt=0
KGX Atomic Operation Log 70000002eb549c0
Mutex 0(0, 0) idn 0 oper NONE
Library Cache uid 113 efd 0 whr 0 slp 0
KGX Atomic Operation Log 70000002eb54a08
Mutex 0(0, 0) idn 0 oper NONE
Library Cache uid 113 efd 0 whr 0 slp 0
SO: 70000006ae53108, type: 53, owner: 70000006f5a5a50, flag: INIT/-/-/0x00
LIBRARY OBJECT LOCK: lock=70000006ae53108 handle=70000002e8e8150 mode=N
call pin=0 session pin=0 hpc=0000 hlc=0000
htl=70000006ae53188[70000006a753478,70000006abaf090] htb=70000006abaf090 ssga=70000006abae018
user=70000006f5a5a50 session=70000006f5a5a50 count=1 flags=CBK[0020] savepoint=0x0
LIBRARY OBJECT HANDLE: handle=70000002e8e8150 mtx=70000002e8e8280(0) cdp=0
namespace=CRSR flags=RON/KGHP/PN0/EXP/[10010100]
kkkk-dddd-llll=0000-0001-0001 lock=N pin=S latch#=4 hpc=0000 hlc=0000
lwt=70000002e8e81f8[70000002e8e81f8,70000002e8e81f8] ltm=70000002e8e8208[70000002e8e8208,70000002e8e8208]
pwt=70000002e8e81c0[70000002e8e81c0,70000002e8e81c0] ptm=70000002e8e81d0[70000002e8e81d0,70000002e8e81d0]
ref=70000002e8e8228[70000004ad30028,70000004ad30028] lnd=70000002e8e8240[70000002e8e8240,70000002e8e8240]
LIBRARY OBJECT: object=70000004ad2f990
type=CRSR flags=EXS[0001] pflags=[0000] status=VALD load=0
DEPENDENCIES: count=1 size=16
AUTHORIZATIONS: count=1 size=16 minimum entrysize=16
ACCESSES: count=1 size=16
TRANSLATIONS: count=1 size=16
DATA BLOCKS:
data# heap pointer status pins change whr
0 70000006eada130 70000004ad2faa8 I/P/A/-/- 0 NONE 00
6 70000004ad2fec8 700000040f57a78 I/P/A/-/E 0 NONE 00
----------------------------------------Oracle handles dead lock by its own. but to resolve the issue u can try following things.
1. take explain for UPDATE MGMT_OMS_PARAMETERS SET VALUE=TO_CHAR(SYSDATE, 'DD-Mon-YYYY HH24:MI:SS') WHERE HOST_URL=:B1 AND NAME='TIMESTAMP';
2. analyze above explain plan and try to tune it.
i think, its because of missing indexes.
Maybe you are looking for
-
Having Problems connecting MacBook Pro to Panasonic TV
Hello Forum! This is my first post on here. I am a long time mac lover and have recently been trying to connect my MacBook Pro to my 42inch Panasonic Viera TV (TX-P42X10B) I am using a DVI to VGA adapter and then a VGA to HDMI cable. Now my MacBook d
-
Can't access game center using nickname from second account
I have two Apple IDs associated with two different e-mail addresses. I set up a game center account with one address and another account with the second address and different ID. After my ipad had to be reset following a crash during the upgrade to
-
INSTALLING OSX ON MY G3 POWERBOOK?
Hi!, I have a G3 powerbook and want to Upgrade my Operating System to OS X. Here's the specs: 1998 Powerbook G3 14.1 TFT/300Mhz/1MB/64MB/8GB HD/4MB Video/DVD/ Modem/ Family Number#M4753 Current Operating System: 9.2.2 More Info: I looked on the Apple
-
Album artwork not right....
I'm having a problem with the album artwork on my iPod Touch 4th Gen....the artwork that shows on itunes doesn't match with what shows on my ipod, even when I go in to edit it to the correct artwork something different shows up on the screen. Does a
-
Wscript.sleep Problem please help!!!!!!
Hi, I'm just a newbie with SAP GUI API. I'm recording SAP and saving the script and making changes to it in Visual basic.net I'm running version SAP 6.40 I think. Below is the code which is generated by SAP record function. And I have added some chan