Shulou(Shulou.com)05/31 Report--

This article mainly introduces "oracle different transaction isolation levels and v$transaction flag column analysis". In daily operation, I believe many people have doubts about oracle different transaction isolation levels and v$transaction flag column analysis. The editor consulted all kinds of data and sorted out simple and easy-to-use operation methods. I hope it will be helpful to answer the doubts of "oracle different transaction isolation levels and v$transaction flag column analysis". Next, please follow the editor to study!

Preface

Oracle can query v$transaction to learn about the execution of database transactions in real time. V$transaction has a column flag, which attracts my attention. See below:

Extended reading

One of the thoughts on the transaction lock lock mode of oracle database transaction

Oracle provides two transaction isolation levels, read committed and serializable. The former is the default value. If you initiate a database transaction with a different transaction isolation level

What's the difference between v$transaction and flag?

Performance of different transaction isolation levels read committed transaction isolation level

Transaction isolation level read committed. The transaction flag generated by all kinds of dml is 3587SQL > set transaction isolation level read committed name 'tran76';Transaction set.SQL > insert into t_test select 3pm 3 from dual. 1 row created.SQL > / NAME ADDR FLAG-- tran76 00000000843521C0 3587SQL > delete from t_test where axi1 1 row deleted.SQL > / NAME ADDR FLAG-- tran76 00000000843521C0 3587SQL > update t_test set axi11 2 rows updated.SQL > / NAME ADDR FLAG-- tran76 00000000843521C0 3587serializable transaction isolation level transaction isolation level serializable flag of transactions generated by various dml are all 268439043SQL > set transaction isolation level serializable name 'tran76' Transaction set.SQL > insert into t_test select 3 from dual;1 row created.SQL > select addr,flag from vicious transactionistADDR FLAG--00000000840B04D8 268439043SQL > update t_test set astat11 where astat1 1 row updated.SQL > / NAME ADDR FLAG-- tran76 00000000843521C0 268439043SQL > delete from t_test 2 rows deleted.SQL > / NAME ADDR FLAG-- tran76 00000000843521C0 268439043SQL > select addr,flag from v$transaction The transaction isolation level lock table generated by the ADDR FLAG--00000000840B04D8 268439043lock mode statement does not generate transactions, nor does it generate flagSQL > lock table t_test in row share mode;Table (s) Locked.SQL > lock table t_test in row exclusive mode;Table (s) Locked.SQL > lock table t_test in share row exclusive mode of transactions. Table (s) Locked.SQL > lock table t_test in exclusive mode;Table (s) Locked.SQL > lock table t_test in share mode;Table (s) Locked.

Thinking

-you can write about flag. You can know what kind of transaction is the transaction isolation level select name,addr,flag,decode (flag,'268439043','serializable','3587','read committed') from v$transaction where addr= (select taddr from v$session where sid=76) NAME ADDR FLAG DECODE (FLAG '2mura-- tran76 00000000843521C0 268439043 serializable here The study on "oracle different transaction isolation levels and v$transaction flag column analysis" is over. I hope to be able to solve your doubts. The collocation of theory and practice can better help you learn, go and try it! If you want to continue to learn more related knowledge, please continue to follow the website, the editor will continue to work hard to bring you more practical articles!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.