dumpshq 1Z0-084 Oracle Database 19c: Performance Management and Tuning VERIFIED QUESTIONS ANSWERS BY Duncan

09-08-2024 10QA - Page 1

Free Questions for 1Z0-084

Shared by Duncan on 09-08-2024
For More Free Questions and Preparation Resources

Check the Links on Last Page

 dumpshq 1Z0-084 Oracle Database 19c: Performance Management and Tuning VERIFIED QUESTIONS ANSWERS BY Duncan
09-08-2024 10QA - Page 2

Question 1
Question Type: MultipleChoice

A Standard Edition production database has performance problems for two hours on the same
day each week.

Which tool must you use to diagnose the problem?

Options:
A- SQL Performance Analyzer
B- AWR Compare Periods report
C- Database Replay
D- Statspack report

Answer:
D

Explanation:
For a Standard Edition production database, the Statspack tool is available to diagnose
performance problems. The Automatic Workload Repository (AWR) and its related tools like AWR
Compare Periods report and SQL Performance Analyzer are features of the Oracle Database
Enterprise Edition and are not available in Standard Edition. Database Replay is also a feature of
the Enterprise Edition. Statspack is a performance diagnostic tool provided for earlier versions
and Standard Editions of the Oracle Database to collect, store, and analyze performance data.

Reference

Oracle Database 19c Administrator's Guide - Using Statspack to Diagnose Database Performance
Issues

Question 2
Question Type: MultipleChoice

Which two statements are true about session wait information contained in v$session or
v$session_wait?
 dumpshq 1Z0-084 Oracle Database 19c: Performance Management and Tuning VERIFIED QUESTIONS ANSWERS BY Duncan
09-08-2024 10QA - Page 3

Options:
A- Rows for sessions displaying WAITED UNKNOWN TIME in the STATE column indicate that the
session is still waiting.
B- Rows for sessions that are currently waiting have a wait time of 0.
C- Rows for sessions that are not waiting might contain the actual wait time for the last event for
which they waited.
D- Rows for sessions that are currently waiting have their wait time incremented every
microsecond.
E- Rows for sessions that are not waiting always contain the total wait time since the session
started.

Answer:
B, C

Explanation:
In the V$SESSION view, Oracle provides information about the session waits:

B) When the WAIT_TIME column has a value of 0, it signifies that the session is currently waiting
for a resource. This column represents the duration of the current or last wait.

C) If the session is not actively waiting, the WAIT_TIME column shows the time the session spent
waiting for the last wait event. If the STATE column is showing 'WAITED KNOWN TIME', it means
the session is not currently waiting, but it indicates the time for which it had waited.

Oracle Database Reference, 19c

Oracle Database Performance Tuning Guide, 19c

Question 3
Question Type: MultipleChoice

This error occurred more than four hours ago in the database:

ORA-04036 PGA memory used by the instance exceeds PGA_AGGREGATE_LIMIT

You want to know which process and query were at fault.

Which two views should you use for this purpose?

 dumpshq 1Z0-084 Oracle Database 19c: Performance Management and Tuning VERIFIED QUESTIONS ANSWERS BY Duncan
09-08-2024 10QA - Page 4

Options:
A- DBA_HIST_ACTIVE_SESS_HISTORY
B- DBA_HIST_SQLSTAT
C- DBA_HIST_SQLTEXT
D- DBA_HIST_PGASTAT
E- DBA_HIST_PROCESS_MEM_SUMMARY

Answer:
A, E

Explanation:
To investigate the cause of the ORA-04036 error, which indicates that PGA memory usage
exceeds the PGA_AGGREGATE_LIMIT, the appropriate views to consult are
DBA_HIST_ACTIVE_SESS_HISTORY and DBA_HIST_PROCESS_MEM_SUMMARY.

DBA_HIST_ACTIVE_SESS_HISTORY: This view provides historical information about active sessions

in the database. It includes details about the SQL executed, the execution context, and the
resources consumed by each session. By examining this view, you can identify the specific
sessions and SQL queries that were active and potentially consuming excessive PGA memory
around the time the ORA-04036 error occurred.

DBA_HIST_PROCESS_MEM_SUMMARY: This view contains historical summaries of memory usage

by processes. It can help in identifying the processes that were consuming a significant amount
of PGA memory, leading to the ORA-04036 error. This view provides aggregated memory usage
information over time, making it easier to pinpoint the processes responsible for high PGA
memory consumption.

Together, these views offer a comprehensive overview of the memory usage patterns and
specific queries or processes that might have contributed to exceeding the
PGA_AGGREGATE_LIMIT, resulting in the ORA-04036 error.

Oracle Database Reference: DBA_HIST_ACTIVE_SESS_HISTORY

Oracle Database Reference: DBA_HIST_PROCESS_MEM_SUMMARY

Oracle Database Performance Tuning Guide: Managing Memory

Question 4
Question Type: MultipleChoice
dumpshq 1Z0-084 Oracle Database 19c: Performance Management and Tuning VERIFIED QUESTIONS ANSWERS BY Duncan
09-08-2024 10QA - Page 5

A database instance is suffering poor I/O performance on two frequently accessed large tables.

No Big Table caching occurs in the database.

Examine these parameter settings:

Which are two actions either one of which will allow Big Table caching to occur?

Options:
A- Increasing DB_BIG_TABLE_CACHE_PERCENT_TARGET to at least 50
B- Setting DB_KEEP_CACHE_SIZE to at least 50M
C- Increasing DB_BIG_TABLE_CACHE_PERCENT_TARGET to at least 25
D- Increasing DB_CACHESIZE to 1 G
E- Setting PARALLEL_DEGREE_POLICYADAPTIVE
F- Setting PARALLEL_DEGREE_POLICYAUTO

Answer:
C, D

Explanation:
Big Table caching is a feature that allows frequently accessed large tables to be cached in
memory to improve I/O performance. From the parameter settings provided, Big Table caching is
not occurring because DB_BIG_TABLE_CACHE_PERCENT_TARGET is set to 10, which is the
minimum threshold for enabling the feature, but the size of the cache is too small for the big
tables to be effectively cached.

To enable Big Table caching, one of the following actions could be taken:

C (Correct): Increasing DB_BIG_TABLE_CACHE_PERCENT_TARGET to at least 25. This action would

allocate a larger percentage of the buffer cache for storing big tables, which could allow for
caching large tables and thus improve I/O performance.

D (Correct): Increasing DB_CACHE_SIZE to 1G. Since the size of the buffer cache is a determining
factor for how much data can be cached, increasing this parameter would provide more memory
space for big tables to be cached.

Options A, B, E, and F will not enable Big Table caching because:

 dumpshq 1Z0-084 Oracle Database 19c: Performance Management and Tuning VERIFIED QUESTIONS ANSWERS BY Duncan
09-08-2024 10QA - Page 6
A: Increasing DB_BIG_TABLE_CACHE_PERCENT_TARGET to 50 without adjusting the overall size of
the cache might still not be sufficient if the DB_CACHE_SIZE is not large enough to hold the big
tables.

B: Setting DB_KEEP_CACHE_SIZE to at least 50M only specifies a separate buffer pool for objects
with the KEEP cache attribute and does not affect Big Table caching.

E: and F: Changing the PARALLEL_DEGREE_POLICY to ADAPTIVE or AUTO influences the behavior

of parallel execution but does not directly enable or influence Big Table caching.

Oracle Database Performance Tuning Guide: Big Table Caching

Oracle Database Reference: DB_BIG_TABLE_CACHE_PERCENT_TARGET

Oracle Database Reference: DB_CACHE_SIZE

Question 5
Question Type: MultipleChoice

Which procedure gathers statistics that are always used in the generation of any execution plan?

Options:
A- DBMS_STATS.GATHER_DICTIONARY_STATS
B- DBMS_STATS.GATHER_FIXED_ OBJECTS_STATS
C- DBMS_STATS.GATHER_DATABASE_STATS
D- DBMS_STATS.GATHER_SYSTEM_STATS

Answer:
C

Explanation:
The DBMS_STATS.GATHER_DATABASE_STATS procedure is used to gather statistics for all schema
objects in the database that do not have up-to-date statistics. These statistics are essential for
the optimizer to make informed decisions about the most efficient way to execute a query. The
procedure collects statistics such as table and column statistics, index statistics, and system
statistics, which are all used in the execution plan generation.

Oracle Database PL/SQL Packages and Types Reference, 19c

 dumpshq 1Z0-084 Oracle Database 19c: Performance Management and Tuning VERIFIED QUESTIONS ANSWERS BY Duncan
09-08-2024 10QA - Page 7
Oracle Database Performance Tuning Guide, 19c

Question 6
Question Type: MultipleChoice

Examine this AWR report excerpt:

You must reduce the impact of database I/O, without increasing buffer cache size and without
modifying the SQL statements.

Which compression option satisfies this requirement?

Options:
A- MN STORE COMPRESS FOR QUERY LOW
B- STORE COMPRESS
C- ROW STORE COMPRESS ADVANCED
D- COLUMN STORE COMPRESS FOR QUERY HIGH

Answer:
C

Explanation:
To reduce the impact of database I/O without increasing the size of the buffer cache and without
modifying SQL statements, you can use table compression. Among the given options, ROW
 dumpshq 1Z0-084 Oracle Database 19c: Performance Management and Tuning VERIFIED QUESTIONS ANSWERS BY Duncan
09-08-2024 10QA - Page 8
STORE COMPRESS ADVANCED is the most suitable form of table compression to satisfy this
requirement.

Advanced row compression (ROW STORE COMPRESS ADVANCED) is designed to work well with all
supported types of data, whether it's OLTP or data warehouse environments. It offers a higher
level of compression than basic table compression (ROW STORE COMPRESS BASIC) without
significant overhead during DML operations. This feature can help reduce the amount of I/O
required to retrieve data by storing it more efficiently on disk.

A, B, D: While COLUMN STORE COMPRESS FOR QUERY HIGH and ROW STORE COMPRESS are both
valid compression types, COLUMN STORE COMPRESS FOR QUERY HIGH applies to the In-Memory
column store and is not available in all versions and editions, and ROW STORE COMPRESS is less
advanced than ROW STORE COMPRESS ADVANCED.

Oracle Database Concepts Guide: Table Compression

Oracle Database Performance Tuning Guide: Row Compression

Question 7
Question Type: MultipleChoice

Examine these statements and output:

What parameter change activates the generation and use of SQL Plan Directives7
 dumpshq 1Z0-084 Oracle Database 19c: Performance Management and Tuning VERIFIED QUESTIONS ANSWERS BY Duncan
09-08-2024 10QA - Page 9

Options:
A- optimizer_features_enable=12.2.0.1
B- optimizer_capture_sql_plan_baselines_TRUE
C- optimizer_dynamic_sampling=11
D- optimizer_adaptive_plans=TRUE
E- optimizer_adaptive_statistics = TRUE

Answer:
E

Explanation:
The optimizer_adaptive_statistics parameter, when set to TRUE, enables the optimizer to use
adaptive statistics, such as SQL Plan Directives, to help improve plans by automatically adjusting
them based on the actual execution statistics.

Oracle Database SQL Tuning Guide, 19c

Question 8
Question Type: MultipleChoice

What is the right time to stop tuning an Oracle database?

Options:
A- When the allocated budget for performance tuning has been exhausted
B- When all the concurrency waits are eliminated from the Top 10
C- When the buffer cache and library cache hit ratio is above 95%
D- When the I/O is less than 10% of the DB time

Answer:
A

Explanation:
The right time to stop tuning an Oracle database is often determined by the point of diminishing
 dumpshq 1Z0-084 Oracle Database 19c: Performance Management and Tuning VERIFIED QUESTIONS ANSWERS BY Duncan
09-08-2024 10QA - Page 10
returns - when the cost of further tuning (in terms of time, resources, or money) exceeds the
performance benefits gained. This is often related to the budget allocated for performance
tuning.

A (Correct): When the allocated budget for performance tuning has been exhausted, it may be
time to stop tuning unless the benefits of further tuning justify requesting additional budget.

B (Incorrect): Eliminating all concurrency waits from the Top 10 is an unrealistic goal since some
waits are inevitable and can occur due to application design, which might not be possible to
eliminate completely.

C (Incorrect): The buffer cache and library cache hit ratio being above 95% does not necessarily
indicate that the database is fully optimized. Hit ratios are not reliable indicators of database
performance and should not be used as sole criteria to end tuning efforts.

D (Incorrect): Having I/O less than 10% of DB time is not a definitive indicator to stop tuning. It is
essential to consider the overall performance goals and whether they have been met rather than
focusing solely on I/O metrics.

Oracle Database Performance Tuning Guide: Introduction to Performance Tuning

Oracle Database 2 Day + Performance Tuning Guide: Understanding the Tuning Process

Question 9
Question Type: MultipleChoice

Which three statements are true about server-generated alerts?

Options:
A- They are notifications from the Oracle Database Server of an existing or impending problem.
B- They provide notifications but never any suggestions for correcting the identified problems.
C- They are logged in the alert log.
D- They can be viewed only from the Cloud Control Database home page.
E- Their threshold settings can be modified by using DBMS_SERVER_ALERT.
F- They may contain suggestions for correcting the identified problems.

Answer:
A, C, F
 dumpshq 1Z0-084 Oracle Database 19c: Performance Management and Tuning VERIFIED QUESTIONS ANSWERS BY Duncan
09-08-2024 10QA - Page 11

Explanation:
Server-generated alerts in Oracle Database are designed to notify DBAs and other administrators
about issues within the database environment. These alerts can be triggered by a variety of
conditions, including threshold-based metrics and specific events such as ORA- error messages.
Here's how these options align with the statements provided:

A (True): Server-generated alerts are indeed notifications from the Oracle Database Server that
highlight existing or impending issues. These alerts are part of Oracle's proactive management
capabilities, designed to inform administrators about potential problems before they escalate.

C (True): These alerts are logged in the alert log of the Oracle Database. The alert log is a crucial
diagnostic tool that records major events and changes in the database, including server-
generated alerts. This log is often the first place DBAs look when troubleshooting database
issues.

F (True): Server-generated alerts may include suggestions for correcting identified problems.
Oracle Database often provides actionable advice within these alerts to assist in resolving issues
more efficiently. These suggestions can range from adjusting configuration parameters to
performing specific maintenance tasks.

Options B, D, and E do not accurately describe server-generated alerts:

B (False): While the statement might have been true in some contexts, Oracle's server-generated
alerts often include corrective suggestions, making this statement incorrect.

D (False): Server-generated alerts can be viewed from various interfaces, not just the Cloud
Control Database home page. They are accessible through Enterprise Manager, SQL Developer,
and directly within the database alert log, among other tools.

E (False): While it's true that threshold settings for some alerts can be modified, the method
specified, using DBMS_SERVER_ALERT, is not correct. Threshold settings are typically adjusted
through Enterprise Manager or by modifying specific initialization parameters directly.

Oracle Database Documentation: Oracle Database 19c: Performance Management and Tuning

Oracle Base: Alert Log and Trace Files

Oracle Support: Understanding and Managing Server-Generated Alerts

Question 10
Question Type: MultipleChoice

Examine this code block, which executes successfully:

dumpshq 1Z0-084 Oracle Database 19c: Performance Management and Tuning VERIFIED QUESTIONS ANSWERS BY Duncan
09-08-2024 10QA - Page 12
DBMS_SERVER_ALERT. SET_THRESHOLD (

DBMS_SERVER_ALERT.CPU_TIME_PER_CALL, DBMS_SERVER_ALERT. OPERATOR_GE, '8000',

DBMS_SERVER_ALERT.OPERATOR_GE, '10000', 1, 2, 'inst1',

DBMS_SERVER_ALERT.OBJECT_TYPE_SERVICE, 'main.regress.rdbms.dev.us.example.com') ;

What will happen?

Options:
A- A warning alert will be issued when CPU time exceeds 1 minute for each user call.
B- A critical alert will be issued when CPU time exceeds 10000 microseconds for each user call.
C- A warning alert will be issued only when CPU time exceeds 10000 microseconds for each user
call.
D- A critical alert will be issued when CPU time exceeds 2 minutes for each user call.

Answer:
B

Explanation:
In the provided code block, the DBMS_SERVER_ALERT.SET_THRESHOLD procedure is used to set
alert thresholds for the CPU time per call in Oracle Database. This procedure is a part of Oracle's
Database Server Alert system, which monitors various metrics and generates alerts when certain
thresholds are exceeded.

The parameters passed to the SET_THRESHOLD procedure are as follows:

The first parameter DBMS_SERVER_ALERT.CPU_TIME_PER_CALL specifies the metric for which the
threshold is being set, in this case, the CPU time consumed per database call.

The second and third parameters DBMS_SERVER_ALERT.OPERATOR_GE and '8000' specify the
warning threshold level and its value, respectively. However, these are not relevant to the
answer as they are overridden by the critical threshold settings.

The fourth and fifth parameters DBMS_SERVER_ALERT.OPERATOR_GE and '10000' set the critical
threshold level and its value. This means that a critical alert will be generated when the CPU time
per call exceeds 10000 microseconds.
dumpshq 1Z0-084 Oracle Database 19c: Performance Management and Tuning VERIFIED QUESTIONS ANSWERS BY Duncan
09-08-2024 10QA - Page 13
The remaining parameters specify the warning and critical alert intervals, the instance name, the
object type, and the service name. These are not directly relevant to the behavior described in
the options.

Thus, the correct answer is B, as the critical threshold for CPU time per call is set to 10000
microseconds, and the system is configured to issue a critical alert when this threshold is
exceeded.

Oracle Database 19c documentation on the DBMS_SERVER_ALERT.SET_THRESHOLD procedure,

which details the parameters and usage of this procedure for setting alert thresholds within
Oracle Database monitoring system.

Oracle Database Performance Tuning Guide, which provides best practices and methodologies for
monitoring and tuning Oracle Database performance, including the use of server alerts and
thresholds.
dumpshq 1Z0-084 Oracle Database 19c: Performance Management and Tuning VERIFIED QUESTIONS ANSWERS BY Duncan
09-08-2024 10QA - Page 14

To Get Premium Files for 1Z0-084 Visit

https://www.p2pexams.com/products/1z0-084

For More Free Questions Visit

https://www.p2pexams.com/oracle/pdf/1z0-084