1Z0-997-25 Question 88
Single answerYou manage an Oracle Database system running on Oracle Cloud Infrastructure (OCI) that encounters a daily spike in CPU usage around midday. Further investigation shows that large reporting queries are executed by analytic users at that time, affecting overall database performance. Which approach in the OCI console is most effective for quickly identifying the top consuming queries in real time so you can address the performance issue?
- A
Use Performance Hub in the OCI Database Management console to review active sessions and top SQL statements.
- B
Initiate a manual RMAN backup to capture all SQL operations and then analyze the backup logs.
- C
Immediately scale up the DB system shape to add more OCPUs and memory to handle the load.
- D
Create a new Pluggable Database (PDB) dedicated to reporting and migrate all reporting users there.
Show answer and explanation
Correct answer: A
Explanation
Performance Hub in the OCI Database Management console provides powerful real-time and historical performance monitoring capabilities, enabling you to quickly identify top SQL statements, active sessions, and wait events. By reviewing this information, you can determine which queries are consuming excessive CPU resources and take targeted actions such as query tuning or resource management. For more details, consult Oracle� Database Management documentation on how to use Performance Hub for performance diagnostics.
- A. Correct.
Correct. Performance Hub in the OCI Database Management console is designed to offer real-time insights into active sessions, top SQL statements, and bottlenecks. This allows you to identify and address the specific queries causing high CPU usage without blindly increasing resources.
- B. Incorrect.
Incorrect. RMAN backups are not intended for real-time query analysis. While logs may contain some information about SQL operations, this approach will not help you quickly pinpoint the top-consuming queries during a performance spike.
- C. Incorrect.
Incorrect. Scaling up resources might temporarily alleviate symptoms, but it does not help you determine which specific queries are causing the spike. Without investigating and optimizing the problematic SQL, additional resources could be wasted.
- D. Incorrect.
Incorrect. Although separating reporting workloads can be a strategy, simply creating a new PDB does not resolve the immediate need to discover which queries are causing the issue. You still need proper monitoring and diagnostics to pinpoint problematic SQL.