1Z0-058 · Question #133
The Global Cache Block Access Latency chart shows high elapsed times. What are two possible causes for this?
The correct answer is A. badly written SQL statements D. slow or faulty interconnect. About Global Cache Block Access Latency Chart If the Global Cache Block Access Latency chart shows high latencies (high elapsed times), then this can be caused by any of the following: A high number of requests caused by SQL statements that are not tuned. A large number of…
Question
The Global Cache Block Access Latency chart shows high elapsed times. What are two possible causes for this?
Options
- Abadly written SQL statements
- Bstorage network bottlenecks
- Ca large number of requested blocks not cached in any instance
- Dslow or faulty interconnect
How the community answered
(30 responses)- A70% (21)
- B20% (6)
- C10% (3)
Explanation
About Global Cache Block Access Latency Chart If the Global Cache Block Access Latency chart shows high latencies (high elapsed times), then this can be caused by any of the following: A high number of requests caused by SQL statements that are not tuned. A large number of processes in the queue waiting for the CPU, or scheduling delays. Slow, busy, or faulty interconnects. In these cases, check your network connection for dropped packets, retransmittals, or cyclic redundancy check (CRC) errors. Oracle® Database 2 Day + Real Application Clusters Guide 11g Release 2 (11.2)
Topics
Community Discussion
No community discussion yet for this question.