|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Re: SMON: Parallel transaction recovery tried [message #517220 is a reply to message #515356] |
Sun, 24 July 2011 22:21  |
luc_tran
Messages: 31
Registered: October 2010
Location: Viet Nam
|
Member |
 
|
|
It has been 2 weeks since I started to analyse the transactions using Log Miner, and notice that there is always an update statement which raises the rollback
SQL> select to_char(lc.timestamp,'HH24:MI:SS') "time",
2 lc.machine_name,
3 lc.username,
4 lc.operation,
5 lc.rollback,
6 lc.xid,
7 lc.seg_owner, lc.seg_name,
8 lc.sql_redo
9 from v$logmnr_contents lc
10 where lc.xid in (select xid from V$FAST_START_TRANSACTIONS)
11 and operation != 'INTERNAL'
12 order by lc.timestamp desc;
time MACHINE_NA USERNAME OPERATION ROLLBACK XID SEG_OWNER SEG_NAME
---------- ---------- ---------- ---------- --------- ------------------ ---------- ---------------
SQL_REDO
----------------------------------------------------------------------------------------------------
19:24:01 UNKNOWN UNKNOWN ROLLBACK 0 0008000E00093046
rollback;
19:24:01 UNKNOWN UNKNOWN DELETE 1 0008000E00093046 UNKNOWN OBJ# 70561
delete from "UNKNOWN"."OBJ# 70561" where ROWID = 'AAAqwsAF7AACMq0AAD';
19:23:40 UNKNOWN UNKNOWN UPDATE 1 0008000E00093046 UNKNOWN OBJ# 70561
update "UNKNOWN"."OBJ# 70561" set "COL 35" = HEXTORAW('00540001010c008000010000000100001bbbcd07000a4
090000420000000') where ROWID = 'AAAqwsAF7AACMq0AAD';
The alert message "SMON: Parallel transaction recovery tried" occurs at 19:23:56. I guess that the UPDATE statement started at 19:23:40 caused the problem
"OBJ# 70561" sure is the object ID, but "COL 35" seems not to be the column ID. I had logged all the statements which update the column ID 35, result is no one touch that column.
Please can anyone tell me how to find out the name of "COL 35" in the above UPDATE statement?
Thanks very much for your help.
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
