oracle 等待,【Oracle等待事件】Transaction等待

01fac6460a22031b8af8da5848698a70.png

【Oracle等待事件】Transaction等待

注意如果 不当设置了例如10513 level 2的等待事件,那么可能造成该Transaction等待,原因是一些实例CRASH所产生的死事务,将不会被SMON主动回滚,这可能造成部分行数据始终被锁定 而不释放。

Definition:     Wait for a blocking transaction to be rolled back. Continue

waiting until the transaction has been rolled back.

Wait Time:      Wait for up to 1 second for a blocking transaction to be

rolled back. Continue waiting until transaction has been

rolled out.

Parameters:

P1 – Undo Segment No | Slot No within Undo header.

P2 – Wrap Sequence [ max value is UB4MAXVAL ].

P3 – Count

undo seg#

SELECT * FROM v$rollstat WHERE usn =

slot#   This is the slot# within the transaction table that is being

used to store a transaction.

wrap#   Wrap or sequence number of the slot. For each new transaction

this number increases.

count   Number of times that Oracle7 has waited on this transaction.

Commentary:     Used within kctwit() [ General TX wait routine . ]

Once we have acquired the TX enqueue of the transaction we

are waiting for , we must continue waiting until the blocking

transaction has been committed/rolled back. If the transaction

has been aborted, then we are waiting for PMON or SMON

to complete the rollback (We may be waiting for SMON if a

rollback segment needs recovery).

This wait is interleaved with “undo segment recovery”, because

on each ‘loop’ we call ktucun().

Whether we see this event depends on the availability of the

failed transactions enqueue. This wait may be more prevalent in

a 2pc environment.

Dependency:     We are dependent on the transaction being rolled out, but we

could be waiting for either the local PMON, or a PMON from

another instance [parallel server].

The Undo Segment No will tell us which instance we are waiting

for , but at present this will remain an eyeball operation

rather than automating it within ph2.

Validity:    N/A

Advise:         The waiting basically depends on the size of that transaction

that is being rolled back. You may want to check if PMON / SMON

is doing the rollback for a killed session and if so check

Parameter:CLEANUP_ROLLBACK_ENTRIES.

From 7.3 onwards View:X$KTUXE can be used to see the

state of a transaction – it shows the transaction table

entries in the rollback segment header.

Related:        Lock:TX

Note:34540.1 Enqueue Metrics.

Bug:960962   Oracle8 OPS issue which can cause OPS

deferred transaction recovery to take a long

time, hence causing ‘transaction’ waits.

  • 0
    点赞
  • 1
    收藏
    觉得还不错? 一键收藏
  • 0
    评论

“相关推荐”对你有帮助么?

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值