What are two possible reasons for this wait event?

You are managing a three-Instance RAC database. In the AWR report, you notice a gc
current block busy wait event on one of the database Instances, in the cluster top timed
events section. What are two possible reasons for this wait event?

You are managing a three-Instance RAC database. In the AWR report, you notice a gc
current block busy wait event on one of the database Instances, in the cluster top timed
events section. What are two possible reasons for this wait event?

A.
CPU shortages.

B.
Frequently used select statements are causing high disk Input/output contention.

C.
Access to blocks was delayed as the blocks were pinned In exclusive mode for updates
by some sessions.

D.
Access to blocks was delayed by log writes on remote Instance.



Leave a Reply 0

Your email address will not be published. Required fields are marked *