Automatic Shared Memory Management is disabled for one of your database instances. Some SQL statements perform poorly due to excessive hard parse activity, thereby degrading performance. What would be your next step?
A.
Run the SQL Access Advisor.
B.
Run the Memory Advisor for the shared pool.
C.
Run the SQL Tuning Advisor.
D.
Run the Memory Advisor for the Program Global Area.
E.
Run the Memory Advisor for the System Global Area.
Agree with you:
https://blogs.oracle.com/oraclemagazine/using-database-advisors
The shared pool advisor provides information about the estimated parse time in the shared pool for different pool sizes, the buffer cache advisor provides information about physical reads and time for the cache size, and the PGA advisor provides information about cache hit percentage against PGA target memory size.
Memory advisors are available under the following conditions: AMM - Memory Advisor, ASMM - SGA Advisor & PGA Advisor, If MSMM (manual shared memory management) & Automatic PGA Memory Management - Buffer Cache Advisor & PGA Advisor. And, APMM is the default for Oracle databases.
A is wrong. SQL Access Advisor is normally run after the SQL Tuning Advisor, if the latter does not give the required results.
B is wrong. You cannot run the memory advisor for the shared pool only.
C is correct. This is the logical first step in tuning SQL statements when no memory advisors are available to use.
D is wrong. Hard parsing indicates that the statement in not cached in the shared pool, part of the SGA, and has nothing to do with the PGA.
E is wrong. The SGA advisor is only available when running in ASMM mode.
C is correct.
https://docs.oracle.com/en/database/oracle/oracle-database/21/tgsql/sql-tuning-guide.pdf
1.5.1 SQL Tuning Tasks
4. Defining the scope of the problem The scope of the solution must match the scope of the problem. Consider a problem at the database level and a problem at the statement level. For example, the shared pool is too small, which causes cursors to age out quickly, which in turn causes many hard parses. Using an initialization parameter to increase the shared pool size fixes the problem at the database level and improves performance for all sessions. However, if a single SQL statement is not using a helpful index, then changing the optimizer initialization parameters for the entire database could harm overall performance. If a single SQL statement has a problem, then an appropriately scoped solution addresses just this problem with this statement.
B is correct it advises on proper memory size for manual memory configuration when AMM is not in place. see memory architecture for oracle https://docs.oracle.com/en/database/oracle/oracle-database/19/admin/managing-memory.html#GUID-24312D78-522D-4C08-8934-820BE18D34C7
I think C because Memory advisor doesn't exists for shared pool and SQL Tuning Advisor is the only option when Manual Shared Memory management is enabled
B,D and E are false since ASMM is turned off and we cannot run memory advisors, the correct answer is C sql tuning advisor because hard parse is due either shared pool is too small or sql statements are not using bind variables.
B.
A hard parse rate of more than 100 a second indicates that there is a very high
amount of hard parsing on the system. High hard parse rates cause serious
performance issues and must be investigated. Usually, a high hard parse rate is
accompanied by latch contention on the shared pool and library cache latches
I still have the doubt. Run the Memory Advisor for the Program Global Area
upvoted 2 times
...
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
Jatindra
Highly Voted 4 years, 1 month agoAlejandrrro
3 years, 6 months agoFranky_T
Highly Voted 2 years, 1 month agodancymonkey
Most Recent 6 months, 2 weeks agoguretto
7 months, 3 weeks agoLEOC71
8 months, 1 week agomusafir
11 months agoGuhborges
1 year agokaka321
1 year ago_gio_
1 year, 3 months agohilaire
1 year, 11 months agoerial
2 years, 3 months agonobody347
2 years, 10 months agoDhanushbh
3 years, 1 month agoasefa
3 years, 6 months agoklever35
4 years, 1 month ago