What are two possible reasons for these wait events?

You are managing a policy-managed three-instance RAC database. You ran database
ADDM for the database and noticed gc current block congested and gc cr block congested
waits. What are two possible reasons for these wait events?

You are managing a policy-managed three-instance RAC database. You ran database
ADDM for the database and noticed gc current block congested and gc cr block congested
waits. What are two possible reasons for these wait events?

A.
The wait events indicate that there is block contention resulting in multiple requests for
access to local blocks.

B.
The wait events indicate that the local instance making the request for current or
consistent read blocks was waiting for logical I/O from its own buffer cache at the same
time.

C.
The wait events indicate a delay in processing has occurred in the Global Cache
Services (GCS), which is usually caused by high load.

D.
The wait times indicate that the blocks must wait after initiating a gc block request, for the
round trip from the start of the wait until the blocks arrive.

Explanation:



Leave a Reply 0

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