次の認定試験に速く合格する！

簡単に認定試験を準備し、学び、そして合格するためにすべてが必要だ。

会員センター  カート (0)
  • ホーム
  • ブログ
  • 最新の[2025年02月28日]1Z0-084試験問題集で有効で更新された問題集 [Q26-Q41]

最新の[2025年02月28日]1Z0-084試験問題集で有効で更新された問題集 [Q26-Q41]

Share

最新の[2025年02月28日]1Z0-084試験問題集で有効で更新された問題集

無料お試しまもなく終了！100%有効な1Z0-084試験問題集には57問があります


この試験では、SQLチューニング、メモリ管理、データベースの統合、データベースの分割など、さまざまなパフォーマンスチューニングの概念に関する候補者の理解をテストします。この試験では、AWRレポート、SQLトレース、リアルタイムSQLモニタリングなど、パフォーマンスの監視とチューニングのためのさまざまなツールとテクニックの使用についてもカバーしています。


Oracle 1Z0-084試験に合格することは、Oracle Database 19cのパフォーマンスを管理・最適化する能力を示すことで、どんなITプロフェッショナルにとっても大きな成果です。この領域での認定は、雇用主から高く評価され、より良い求人機会や高い給与につながる可能性があります。試験勉強には、データベースパフォーマンスチューニングの概念に関する強い理解とOracle Database 19cで幅広い実務経験が必要です。

 

質問 # 26
Which two types of performance problems are reported by ADDM for PDBS?

  • A. Top SQL statements
  • B. Excessive checkpoint writes
  • C. I/O capacity limits
  • D. SGA sizing issues
  • E. User I/O waits

正解：C、E

解説：
The Automatic Database Diagnostic Monitor (ADDM) analyzes and reports on various types of performance problems. For Pluggable Databases (PDBs), it can identify issues such as I/O capacity limits which may hinder the overall performance by causing bottlenecks. Additionally, ADDM can report on user I/O waits, which can indicate performance issues related to the time it takes for user queries to read data from the disk.
References:
* Oracle Multitenant Administrator's Guide, 19c
* Oracle Database Performance Tuning Guide, 19c


質問 # 27
Examine this statement and output:

Which two situations can trigger this error?

  • A. There is a file in the capture directory.
  • B. The instance is unable to access the capture directory.
  • C. The user lacks the required privileges to execute the DBMS WORKLOAD CAPTURE package or the directory.
  • D. The capture directory is part of the root file system.
  • E. The syntax is incomplete.

正解：B、C

解説：
The ORA-15505 error indicates that the instance encountered errors while trying to access the specified directory. This could be due to:
A: Insufficient privileges: The user attempting to start the workload capture might not have the required permissions to execute the DBMS_WORKLOAD_CAPTURE package or to read/write to the directory specified.
E: Accessibility: The database instance may not be able to access the directory due to issues such as incorrect directory path, directory does not exist, permission issues at the OS level, or the directory being on a file system that's not accessible to the database instance.
References:
* Oracle Database Error Messages, 19c
* Oracle Database Administrator's Guide, 19c


質問 # 28
SGA_TARGET and PGA_AGGREGATE_TARGET are configured to nonzero values.
MEMORY_target is then set to a nonzero value but memory_MAX_TARGET is not set.
Which two statements are true?

  • A.
  • B.
  • C.
  • D.
  • E.
  • F.
  • G.

正解：A、D

解説：
When MEMORY_TARGET is set to a nonzero value, Oracle automatically manages the memory allocation between the System Global Area (SGA) and the Program Global Area(PGA). If MEMORY_MAX_TARGET is not explicitly set, Oracle will behave in the following manner:
* MEMORY_MAX_TARGET will default to the value of MEMORY_TARGET, assuming the platform allows for the value of MEMORY_TARGET to be increased dynamically. This means that MEMORY_TARGET represents both the initial allocation and the maximum limit for the dynamically managed memory unless MEMORY_MAX_TARGET is specified differently.
* If MEMORY_TARGET is set to a value that is less than the sum of the current values of SGA_TARGET and PGA_AGGREGATE_TARGET, Oracle will use the higher sum as the default value for MEMORY_MAX_TARGET to ensure that there is adequate memory for both areas. The database instance will not start if MEMORY_TARGET is not sufficient to accommodate the combined SGA and PGA requirements.
References
* Oracle Database Administrator's Guide 19c: Automatic Memory Management
* Oracle Database Performance Tuning Guide 19c: Using Automatic Memory Management


質問 # 29
You manage a 19c database with default optimizer settings.
This statement is used extensively as subquery in the application queries:
SELECT city_id FROM sh2.sales WHERE city_id=:Bl
You notice the performance of these queries is often poor and, therefore, execute:
SELECT city_id,COUNT(*) FROM sh2.sales GROUP BY city_id;
Examine the results:

There is no index on the CITY_ID column.
Which two options improve the performance?

  • A. Use a SQL Profile to enforce the appropriate plan.
  • B. Force the subquery to use dynamic sampling.
  • C. Activate the adaptive plans.
  • D. Create an index on the CITY IP column.
  • E. Generate frequency histograms on the CITY__ID column.

正解：D、E

解説：
In this scenario, creating an index and generating frequency histograms are two methods that can potentially improve performance:
* A (Correct): Generating frequency histograms on the CITY_ID column can help the optimizer make better decisions regarding the execution plan, especially if the data distribution is skewed. Histograms provide the optimizer with more detailed information about the data distribution in a column, which is particularly useful for columns with non-uniform distributions.
* B (Correct): Creating an index on the CITY_ID column would speed up queries that filter on this column, especially if it's used frequently in the WHERE clause as a filter. An index would allow for an index range scan instead of a full table scan, reducing the I/O and time needed to execute such queries.
* C (Incorrect): While SQL profiles can be used to improve the performance of specific SQL statements, they are usually not the first choice for such a problem, and creating a profile does not replace the need for proper indexing or statistics.
* D (Incorrect): Forcing the subquery to use dynamic sampling might not provide a consistent performance benefit, especially if the table statistics are not representative or are outdated. However, dynamic sampling is not as effective as having accurate statistics and a well-chosen index.
* E (Incorrect): Adaptive plans can adjust the execution strategy based on the conditions at runtime.
While they can be useful in certain scenarios, in this case, creating an index and ensuring accurate statistics would likely provide a more significant performance improvement.
References:
* Oracle Database SQL Tuning Guide: Managing Optimizer Statistics
* Oracle Database SQL Tuning Guide: Using Indexes and Clusters


質問 # 30
You must write a statement that returns the ten most recent sales. Examine this statement:

Users complain that the query executes too slowly. Examine the statement's current execution plan:

What must you do to reduce the execution time and why?

  • A. Replace the FETCH FIRST clause with ROWNUM to enable the use of an index on SALES.
  • B. Enable Adaptive Plans so that Oracle can change the Join method as well as the Join order for this query.
  • C. Collect a new set of statistics on PRODUCT, CUSTOMERS, and SALES because the current stats are inaccurate.
  • D. Create an index on SALES.TIME_ID to force the return of rows in the order specified by the ORDER BY clause.
  • E. Create an index on SALES.CUST_ID to force an INDEX RANGE SCAN on this index followed by a NESTED LOOP join between CUSTOMERS and SALES.

正解：D

解説：
The execution plan shows a full table access for the SALES table. To reduce the execution time, creating an index on SALES.TIME_ID would be beneficial as it would allow the database to quickly sort and retrieve the most recent sales without the need to perform a full table scan, which is I/O intensive and slower. By indexing TIME_ID, which is used in the ORDER BY clause, the optimizer can take advantage of the index to efficiently sort and limit the result set to the ten most recent sales.
* B (Incorrect): Replacing FETCH FIRST with ROWNUM would not necessarily improve the performance unless there is an appropriate index that the optimizer can use to avoid sorting the entire result set.
* C (Incorrect): There is no indication that the current statistics are inaccurate; hence, collecting new statistics may not lead to performance improvement.
* D (Incorrect): While adaptive plans can provide performance benefits by allowing the optimizer to adapt the execution strategy, the main issue here is the lack of an index on the ORDER BY column.
* E (Incorrect): Creating an index on SALES.CUST_ID could improve join performance but would not address the performance issue caused by the lack of an index on the ORDER BY column.
References:
* Oracle Database SQL Tuning Guide: Managing Indexes
* Oracle Database SQL Tuning Guide: Using Indexes and Clusters


質問 # 31
Which two types of performance problems are reported by ADDM for PDBS?

  • A. Excessive checkpoint writes
  • B. User I/O waits
  • C. I/O capacity limits
  • D. SGA sizing issues
  • E. Top SQL statements

正解：C、E

解説：
ADDM (Automatic Database Diagnostic Monitor) is a key Oracle diagnostic tool that analyzes performance data captured by AWR (Automatic Workload Repository) and provides insights into performance issues. In a PDB (Pluggable Database), ADDM can provide recommendations for various types of performance issues.
Why A. I/O capacity limits is correct:
* ADDM evaluates the performance of a database and identifies I/O bottlenecks that could be impacting query performance.
* I/O capacity limits occur when the database cannot handle the I/O workload effectively, which could be due to disk contention, inadequate I/O throughput, or hardware limitations.
* ADDM reports such issues and suggests remedies like tuning SQL queries, redistributing I/O workloads, or upgrading storage systems.
Why D. Top SQL statements is correct:
* One of the critical capabilities of ADDM is identifying high-resource-consuming SQL statements (Top SQL) that are impacting database performance.
* For PDBs, ADDM provides specific recommendations to optimize these SQL statements, such as improving execution plans, adding indexes, or rewriting queries.
Why Other Options Are Incorrect:
* B. Excessive checkpoint writes:
* While excessive checkpoint writes can occur, ADDM typically focuses on higher-level performance problems like I/O issues or top SQL rather than specific low-level operational events like checkpointing. Excessive checkpoint writes are not commonly reported directly for PDBs by ADDM.
* C. SGA sizing issues:
* ADDM does not directly analyze or provide recommendations for SGA (System Global Area) sizing issues at the PDB level because SGA is managed at the CDB (Container Database) level.
PDBs share the SGA of the CDB.
* E. User I/O waits:
* While user I/O waits are captured in performance metrics, ADDM typically groups them under broader issues like I/O capacity limits. It does not specifically report on "user I/O waits" as a standalone problem.
Key Features of ADDM for PDBs:
* Identifying Top SQL Statements impacting performance.
* Reporting I/O issues, including capacity limits and contention.
* Highlighting inter-PDB resource contention within the same CDB.
References to Oracle Documentation:
* Oracle Database 19c Performance Tuning Guide:
* Section: Using ADDM for Pluggable Databases.
* Details the types of performance issues ADDM reports for PDBs.
* Automatic Database Diagnostic Monitor (ADDM) Concepts:
* Highlights ADDM's ability to analyze I/O, SQL performance, and resource utilization.


質問 # 32
You must configure and enable Database Smart Flash Cache for a database.
You configure these flash devices:

Examine these parameter settings:

What must be configured so that the database uses these devices for the Database Smart Flash Cache?

  • A. Set DB_FLASH_CACHE_SIZE to 256G and change device /dev/sdk to 128G.
  • B. Set DB_FLASH_CACHE_SIZE parameter to 128G, 64G.
  • C. Disable Automatic Memory Management and set SGA_TARGET to 256G.
  • D. Set DB_FLASH_CACHE_SIZE parameter to 192G.
  • E. Set DB_FLASH_CACHE_SIZE to 192G and MEMORY_TARGET to 256G.

正解：B

解説：
To configure and enable Database Smart Flash Cache, you must set the DB_FLASH_CACHE_SIZE parameter to reflect the combined size of the flash devices you intend to use for the cache. In this scenario, two flash devices are configured: /dev/sdj with 128G and /dev/sdk with 64G.
* Determine the combined size of the flash devices intended for the Database Smart Flash Cache. In this case, it's 128G + 64G = 192G.
* However, Oracle documentation suggests setting DB_FLASH_CACHE_SIZE to the exact sizes of the individual devices, separated by a comma when multiple devices are used.
* Modify the parameter in the database initialization file (init.ora or spfile.ora) or using an ALTER SYSTEM command. Here's the command for altering the system setting:
ALTER SYSTEM SET DB_FLASH_CACHE_SIZE='128G,64G' SCOPE=SPFILE;
* Since this is a static parameter, a database restart is required for the changes to take effect.
* Upon database startup, it will allocate the Database Smart Flash Cache using the provided sizes for the specified devices.
It is important to note that MEMORY_TARGET and MEMORY_MAX_TARGET parameters should be configured independently of DB_FLASH_CACHE_SIZE. They control the Oracle memory management for the SGA and PGA, and do not directly correlate with the flash cache configuration.
References
* Oracle Database 19c Documentation on Database Smart Flash Cache
* Oracle Support Articles and Community Discussions on DB_FLASH_CACHE_SIZE Configuration


質問 # 33
Which three statements are true about tuning dimensions and details of v$sys_time_model and DB time?

  • A. When WAIT TIME is high, instance tuning may improve performance.
  • B. DB Time accounts for all time used by background processes and user sessions.
  • C. The proportion of WAIT TIME to CPU TIME always increases with increased system load.
  • D. Statspack cannot account for high CPU time when CPU TIME is a Top 10 event in DB time. When CPU time is high, SQL tuning may improve performance.
  • E. Parse Time Elapsed accounts for successful soft and hard parse operations only.
  • F. Systems in which CPU time is dominant need more tuning that those in which WAIT TIME is dominant.

正解：A、B、D

解説：
A: Statspack is a performance diagnostic tool that can help identify high CPU usage issues. High CPU time may indicate that SQL statements need to be tuned for better performance.
D: High wait times can often be reduced by instance tuning, such as adjusting database parameters or improving I/O performance.
F: DB Time is a cumulative time metric that includes the time spent by both user sessions and background processes executing database calls.References:
* Oracle Database Performance Tuning Guide, 19c
* Oracle Database Concepts, 19c


質問 # 34
SGA_TARGET and PGA_AGGREGATE_TARGET are configured to nonzero values.
MEMORY_target is then set to a nonzero value but memory_MAX_TARGET is not set.
Which two statements are true?

  • A.
  • B.
  • C.
  • D.
  • E.
  • F.
  • G.

正解：E、G

解説：
When MEMORY_TARGET is set to a nonzero value, Oracle automatically manages the memory allocation between the System Global Area (SGA) and the Program Global Area (PGA). If MEMORY_MAX_TARGET is not explicitly set, Oracle will behave in the following manner:
* MEMORY_MAX_TARGET will default to the value of MEMORY_TARGET, assuming the platform allows for the value of MEMORY_TARGET to be increased dynamically. This means that MEMORY_TARGET represents both the initial allocation and the maximum limit for the dynamically managed memory unless MEMORY_MAX_TARGET is specified differently.
* If MEMORY_TARGET is set to a value that is less than the sum of the current values of SGA_TARGET and PGA_AGGREGATE_TARGET, Oracle will use the higher sum as the default value for MEMORY_MAX_TARGET to ensure that there is adequate memory for both areas. The database instance will not start if MEMORY_TARGET is not sufficient to accommodate the combined SGA and PGA requirements.
References
* Oracle Database Administrator's Guide 19c: Automatic Memory Management
* Oracle Database Performance Tuning Guide 19c: Using Automatic Memory Management


質問 # 35
A database supporting a mixed workload is hosted on a server with 64 CPUs.
A large number of free buffer waits and buffer busy waits occur affecting performance.
The buffer cache size was then increased but after a few hours, the same wait events occur more often than before the change.
Examine these parameter settings:

Which two actions can help reduce the number of these waits7

  • A. setting dbwr_io_slaves to 64
  • B. increasing the value of DBWRITERPROCESSES to 64,
  • C. Increasing the size of MEMORYTARGET
  • D. increasing the value of DB_FILE_MULTIBLOCK_READ_COUNT to 128
  • E. reducing the values of DB_FILE_MULTILOCK_READ_COUNT to 64

正解：A、B

解説：
Given a server with 64 CPUs, if the buffer cache size increase did not alleviate free buffer waits and buffer busy waits, one can look into optimizing I/O and the efficiency of the DB writer processes.
C: Setting theDBWR_IO_SLAVESparameter to a non-zero value, such as the number of CPUs, would initiate I/O slave processes to assist the DB writer process. This can help reduce I/O contention when writing from the buffer cache to disk, particularly for systems without asynchronous I/O capabilities.
D: Increasing the value ofDBWRITERPROCESSESenables multiple DB writer processes to be active simultaneously. In a system with many CPUs, such as 64, increasing this value can improve the write throughput to disk and potentially reduce buffer busy waits.
References:
* Oracle Database Reference, 19c
* Oracle Database Performance Tuning Guide, 19c


質問 # 36
This error occurred more than four hours ago in the database:
ORA-04036 PGA memory used by theinstance exceedsPGA_AGGREGATE_LIMIT
You want to know which process and query were at fault.
Which two views should you use for this purpose?

  • A. DBA_HIST_SQLSTAT
  • B. DBA_HIST_SQLTEXT
  • C. DBA_HIST_PGASTAT
  • D. DBA_HIST_PROCESS_MEM_SUMMARY
  • E. DBA_HIST_ACTIVE_SESS_HISTORY

正解：D、E

解説：
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_HISTORYandDBA_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 thePGA_AGGREGATE_LIMIT, resulting in the ORA-04036 error.
References:
* Oracle Database Reference:DBA_HIST_ACTIVE_SESS_HISTORY
* Oracle Database Reference:DBA_HIST_PROCESS_MEM_SUMMARY
* Oracle Database Performance Tuning Guide:Managing Memory


質問 # 37
You must write a statement that returns the ten most recent sales. Examine this statement:

Users complain that the query executes too slowly. Examine the statement's current execution plan:

What must you do to reduce the execution time and why?

  • A. Replace the FETCH FIRST clause with ROWNUM to enable the use of an index on SALES.
  • B. Enable Adaptive Plans so that Oracle can change the Join method as well as the Join order for this query.
  • C. Collect a new set of statistics on PRODUCT, CUSTOMERS, and SALES because the current stats are inaccurate.
  • D. Create an index on SALES.TIME_ID to force the return of rows in the order specified by the ORDER BY clause.
  • E. Create an index on SALES.CUST_ID to force an INDEX RANGE SCAN on this index followed by a NESTED LOOP join between CUSTOMERS and SALES.

正解：D

解説：
The execution plan shows a full table access for theSALEStable. To reduce the execution time, creating an index onSALES.TIME_IDwould be beneficial as it would allow the database to quickly sort and retrieve the most recent sales without the need to perform a full table scan, which is I/O intensive and slower. By indexing TIME_ID, which is used in theORDER BYclause, the optimizer can take advantage of the index to efficiently sort and limit the result set to the ten most recent sales.
* B (Incorrect):ReplacingFETCH FIRSTwithROWNUMwould not necessarily improve the performance unless there is an appropriate index that the optimizer can use to avoid sorting the entire result set.
* C (Incorrect):There is no indication that the current statistics are inaccurate; hence, collecting new statistics may not lead to performance improvement.
* D (Incorrect):While adaptive plans can provide performance benefits by allowing the optimizer to adapt the execution strategy, the main issue here is the lack of an index on theORDER BYcolumn.
* E (Incorrect):Creating an index onSALES.CUST_IDcould improve join performance but would not address the performance issue caused by the lack of an index on theORDER BYcolumn.
References:
* Oracle Database SQL Tuning Guide:Managing Indexes
* Oracle Database SQL Tuning Guide:Using Indexes and Clusters


質問 # 38
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?

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

正解：A、D

解説：
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:
* 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.
References:
* Oracle Database Performance Tuning Guide: Big Table Caching
* Oracle Database Reference: DB_BIG_TABLE_CACHE_PERCENT_TARGET
* Oracle Database Reference: DB_CACHE_SIZE


質問 # 39
What are the least elevated values of statistics_level and C0NTR0LJ4ANAGEMENT_PACK_ACCESS that allow the usage of Monitoring of Database Operations?

  • A. STATISTICS_LEVEL=ALL and
    CONTROL_MANAGEMENT_PACK_ACCESS=DIAGOSTIC+TUNING
  • B. STATISTICS_LEVEL=TYPICAL and CONTROL_MANAGEMENT_PACK_ACCESS=DIAGOSTIC
  • C. STATISTICS_LEVEL=TYPICAL and
    CONTROL_MANAGEMENT_PACK_ACCESS-DIAGOSTIC*TUNING
  • D. STATISTICS_LEVEL=BASIC and CONTROL_MANAGEMENT_PACK ACCESS=DIAGOSTIC

正解：A

解説：
Monitoring of Database Operations requires that theSTATISTICS_LEVELparameter be set toALLand CONTROL_MANAGEMENT_PACK_ACCESSbe set toDIAGNOSTIC+TUNING. These settings enable all the advisory features and automatic tuning features within the Oracle Database, including the Automatic Workload Repository (AWR), Automatic Database Diagnostic Monitor (ADDM), and the full functionality of the SQL Tuning Advisor and SQL Access Advisor, which are components of the Diagnostic and Tuning packs.
* STATISTICS_LEVEL=ALL:This setting enables the collection of all system statistics for problem detection and self-tuning purposes.
* CONTROL_MANAGEMENT_PACK_ACCESS=DIAGNOSTIC+TUNING:This grants access to both the Diagnostic Pack and the Tuning Pack, which are essential for detailed performance monitoring and tuning capabilities.
References:
* Oracle Database Reference:STATISTICS_LEVEL
* Oracle Database Licensing Information User Manual:Oracle Database Management Packs


質問 # 40
The CURS0R_SHARING and OPTIMIZER_CAPTURE_SQL_PLAN_BASELINES parameters are set to default. The top five wait events in an awr report are due to a large number of hard parses because of several almost identical SQL statements.
Which two actions could reduce the number of hard parses?

  • A. Set the CURSOR_SHARING parameter to FORCE.
  • B. Create the KEEP cache and cache tables accessed by the SQL statements.
  • C. Increase the size of the library cache.
  • D. Set OPTIMIZER_CAPTURE_SQL_PLAN_BASELINES to TRUE.
  • E. Create the RECYCLE cache and cache tables accessed by the SQL statements.

正解：A、C

解説：
To reduce the number of hard parses due to several almost identical SQL statements, you can take the following actions:
* C (Correct): Increasing the size of the library cache can help reduce hard parses by providing more memory to store more execution plans. This allows SQL statements to be shared more effectively.
* E (Correct): Setting the CURSOR_SHARING parameter to FORCE will cause Oracle to replace literals in SQL statements with bind variables, which can significantly reduce the number of hard parses by making it more likely that similar SQL statements will share the same execution plan.
The other options do not directly impact the number of hard parses:
* A (Incorrect): Creating the KEEP cache and caching tables accessed by the SQL statements can improve performance for those tables, but it does not directly reduce the number of hard parses.
* B (Incorrect): Creating the RECYCLE cache and caching tables accessed by the SQL statements can make it more likely that objects will be removed from the cache quickly, which does not help with hard parse issues.
* D (Incorrect): Setting OPTIMIZER_CAPTURE_SQL_PLAN_BASELINES to TRUE can help stabilize SQL execution plans but will not reduce the number of hard parses. This parameter is used to automatically capture SQL plan baselines for repeatable SQL statements, which can prevent performance regressions due to plan changes.
References:
* Oracle Database Performance Tuning Guide: Minimizing Hard Parses
* Oracle Database SQL Tuning Guide: CURSOR_SHARING


質問 # 41
......

1Z0-084試験問題集で100%高得点させる1Z0-084試験解答がこちら：https://www.jpntest.com/shiken/1Z0-084-mondaishu

検証済みの1Z0-084試験問題成功確定させます：https://drive.google.com/open?id=1luih6wfsyBJjWBY0l_bg33yxx7frsSOJ

関するブログ

もっと
1Z0-084無料問題集

弊社を連絡する

我々は１２時間以内ですべてのお問い合わせを答えます。

オンラインサポート時間：( UTC+9 ) 9:00-24:00
月曜日から土曜日まで

サポート：現在連絡 

関連リンク

トップ試験