100%合格、売れ筋最上位1z1-084試験材料は2024年最新のOracle練習試験合格させます
Oracle Database 19c問題集で1z1-084試験完全版問題、試験学習ガイド
Oracle 1Z0-084試験は、60の複数選択の質問で構成されるコンピューターベースのテストです。候補者は試験を完了するために120分かかり、合格するには少なくとも63%を獲得する必要があります。試験料は245ドルで、候補者は世界中のピアソンビューテストセンターで試験を受けることができます。 Oracleは、候補者がこの試験を受ける前に、データベースのパフォーマンスとチューニング管理の少なくとも3年の経験があることを推奨しています。
質問 # 15
18. The application provider has given full indications regarding the procedure to collect statistics.
To reduce the space used in the SYSAUX tablespace, you want to prevent the optimizer statistics Advisor from running.
Which method will allow you to do this?
- A. Use DBMS_AUTO_TASK_ADMIN. DISABLE to disable the AUTO_STATS_ADVISOR_TASK task.
- B. Set the AUTO_STATS_ADVISOR_TASK global statistics preference to FALSE.
- C. Use DBMS STATS.DROP ADVISOR TASK to drop the AUTO_STATS_ADVISOR_TASK task.
- D. Set the parameter OPTIMIZER_ADAPTIVE_STATISTICS to FALSE.
正解:A
解説:
The Oracle Optimizer statistics advisor, which is part of the automated tasks framework, can be disabled using the DBMS_AUTO_TASK_ADMIN package. This will prevent it fromrunning and thus reduce space usage in the SYSAUX tablespace.References:
* Oracle Database PL/SQL Packages and Types Reference, 19c
質問 # 16
Which three types of statistics are captured by statspack with snap level 6?
- A. Parent and child latches
- B. Optimizer execution plans
- C. Plan usage data
- D. Enqueue statistics
- E. Segment-level statistics
- F. Parent and child latches
正解:D、E、F
解説:
Statspack is a performance diagnostic tool provided by Oracle prior to the introduction of the Automatic Workload Repository (AWR). At snap level 6, Statspack captures the following types of statistics:
* A (Correct):Parent and child latches are captured. Latch statistics provide information about contention for latches, which are low-level serialization mechanisms used by Oracle.
* E (Correct):Enqueue statistics, which provide information on the waits for locks that manage the concurrency between users.
* F (Correct):Segment-level statistics, which provide detailed information on database segments such as tables, indexes, etc., to identify I/O and contention issues.
* C (Incorrect):While optimizer execution plans are an essential aspect of performance tuning, detailed execution plan capture is not part of the Statspack report at level 6.
* D (Incorrect):Plan usage data refers to how frequently a plan is being used, which is more associated with AWR and not typically captured in Statspack reports.
References:
* Oracle Database Performance Tuning Guide:Using Statspack
質問 # 17
You need to transport performance data from a Standard Edition to an Enterprise Edition database. What is the recommended method to do this?
- A. Export the data by using expdp from the ftatspack repository and import it by using impdp into the AWR repository.
- B. Export the data by using the exp utility and parameter file spuexp.par from the Statspack repository and import it by using imp into a dedicated Statspack schema on the destination.
- C. Export the data by using the expdp utility and parameter file spuexp.par from the Statspack repository and import it by using impdp into Export the data by using expdp from the Statspack repository and import it by using impdp into the AWR repository.
- D. Export the data by using expdp from Statspack and import it by using
$ORACLE_HOME/rdbms/admin/awrload into the AWRrepository.
正解:B
解説:
To transport performance data from an Oracle Database Standard Edition, which uses Statspack, to an Enterprise Edition database, which uses AWR, you must consider the compatibility of data structures and repository schemas between these tools. The recommended method is:
* D (Correct):Export the data using theexputility with a parameter file appropriate for Statspack (like spuexp.par) from the Statspack repository and import it into a dedicated Statspack schema on the destination. Since Statspack and AWR use different schemas, it's not recommended to import Statspack data directly into the AWR repository.
The other options are incorrect because:
* A (Incorrect):expdpis not designed to export from Statspack, andawrloadis intended for loading from an AWR export file, not a Statspack export.
* B (Incorrect):Althoughexpdpandimpdpare used for exporting and importing data, the AWR repository schema is different from the Statspack schema, so importing Statspack data directly into the AWR repository is not recommended.
* C (Incorrect):Usingexpdpto export from Statspack and then importing directly into the AWR repository is not the correct approach due to the schema differences between Statspack and AWR.
References:
* Oracle Database Performance Tuning Guide:Migrating from Statspack to AWR
質問 # 18
Accessing the SALES tables causes excessive db file sequential read wait events.
Examine this AWR except:
Now, examine these attributes displayed by querying dba_tables:
Finally, examine these parameter settings:
Which two must both be used to reduce these excessive waits?
- A. Partition the SALES table.
- B. Compress the SALES table.
- C. Increase PCTFREE for the SALES table.
- D. Re-create the SALES table.
- E. Coalesce all sales table indexes.
正解:A、B
解説:
The AWR excerpt points to excessive physical reads on the SALES table and index, suggesting the need for optimizing table storage and access.
Partitioning the SALES table (A) can reduce 'db file sequential read' waits by breaking down the large SALES table into smaller, more manageable pieces. This can localize the data and reduce the I/O necessary for query operations.
Compressing the SALES table (D) can also help reduce I/O by minimizing the amount of data that needs to be read from disk. This can also improve cache utilization and reduce the 'db file sequential read' waits.
References:
* Oracle Database VLDB and Partitioning Guide, 19c
* Oracle Database Administrator's Guide, 19c
These changes are recommended based on Oracle's best practices for managing large tables and reducing I/O waits, ensuring better performance and efficiency.
質問 # 19
Which two options are part of a Soft Parse operation?
- A. SQL Row Source Generation
- B. Syntax Check
- C. SQL Optimization
- D. Shared Pool Memory Allocation
- E. Semantic Check
正解:E
解説:
During a soft parse, Oracle checks the shared SQL area to see if an incoming SQL statement matches one already in the shared pool. This operation includes syntax and semantic checks. The syntax check ensures the statement is properly formed, and the semantic check confirms that all the objects referenced in the SQL statement exist and that the user has the necessary privileges to access them.References:
* Oracle Database Concepts, 19c
* Oracle Database SQL Tuning Guide, 19c
質問 # 20
During which application lifecycle phase do you take baselines?
- A. Design and development
- B. Deployment
- C. Production
- D. Migration or upgrade
- E. Testing
正解:C
解説:
Baselines are typically taken during the production phase of the application lifecycle. They provide a snapshot of performance metrics under normal operating conditions which can be used for comparison against future performance. Baselines are essential for understanding how the system performs under its typical workload and for detecting deviations from this expected performance over time, especially after changes like migrations, upgrades, or significant changes in user activity.
References
* Oracle Database 19c Performance Tuning Guide - Managing Performance Through Baselines
質問 # 21
You want to reduce the amount of db file scattered read that is generated in the database.You execute the SQL Tuning Advisor against the relevant workload. Which two can be part of the expected result?
- A. recommendations regarding the creation of additional indexes
- B. recommendations regarding the creation of SQL Patches
- C. recommendations regarding partitioning the tables
- D. recommendations regarding the creation of materialized views
- E. recommendations regarding rewriting the SQL statements
正解:A、D
解説:
The SQL Tuning Advisor provides recommendations for improving SQL query performance. This may include suggestions for creating additional indexes to speed up data retrieval and materialized views to precompute and store query results.References:
* Oracle Database SQL Tuning Guide, 19c
質問 # 22
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?
- A. Database Replay
- B. SQL Performance Analyzer
- C. Statspack report
- D. AWR Compare Periods report
正解:C
解説:
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.
References
* Oracle Database 19c Administrator's Guide - Using Statspack to Diagnose Database Performance Issues
質問 # 23
Which two Oracle Database features use database services?
- A. Oracle SQL Performance Management
- B. Oracle SQL Tuning Advisor
- C. Oracle Scheduler
- D. Database Resource Manager
- E. Oracle Automatic Reoptimization
正解:C、D
解説:
Database services in Oracle are used to manage how resources are allocated and how workloads are managed within the database. The features that use database services are:
* B (Correct):Database Resource Manager (DBRM) uses services to control resource allocation to different workloads. It ensures that resources are assigned to the most critical tasks first, based on the service associated with the workload.
* E (Correct):Oracle Scheduler can also utilize database services. Jobs in Oracle Scheduler can be assigned to different services to control resource allocation and prioritization.
The other features mentioned are related to SQL performance but do not directly utilize database services in the way Resource Manager and Scheduler do:
* A:Oracle Automatic Reoptimization is a feature that allows the database to automatically improve the execution plan of a SQL statement after it is executed, based on the actual performance metrics, but it does not directly use database services.
* C:Oracle SQL Performance Management involves various components of SQL tuning and monitoring, but it does not use database services to operate.
* D:Oracle SQL Tuning Advisor provides advice on how to tune SQL queries for better performance.
While it can be used in conjunction with services for managing and analyzing workloads, it doesn't use services in its core functionality.
References:
* Oracle Database Administrator's Guide:Administering Services
* Oracle Database Administrator's Guide:Managing Resources with Oracle Database Resource Manager
* Oracle Database Scheduler Developer's Guide:Using the Scheduler
質問 # 24
You want to reduce the amount of db file scattered read that is generated in the database.You execute the SQL Tuning Advisor against the relevant workload. Which two can be part of the expected result?
- A. recommendations regarding the creation of additional indexes
- B. recommendations regarding the creation of SQL Patches
- C. recommendations regarding partitioning the tables
- D. recommendations regarding the creation of materialized views
- E. recommendations regarding rewriting the SQL statements
正解:A、D
解説:
The SQL Tuning Advisor provides recommendations for improving SQL query performance. This may include suggestions for creating additional indexes to speed up data retrieval and materialized views to precompute and store query results.References:
* Oracle Database SQL Tuning Guide, 19c
質問 # 25
Examine these statements and output:
What parameter change activates the generation and use of SQL Plan Directives7
- A. optimizer_dynamic_sampling=11
- B. optimizer_capture_sql_plan_baselines_TRUE
- C. optimizer_features_enable=12.2.0.1
- D. optimizer_adaptive_plans=TRUE
- E. optimizer_adaptive_statistics = TRUE
正解:E
解説:
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.
References:
* Oracle Database SQL Tuning Guide, 19c
質問 # 26
Which two statements are true about Data Pump import for objects that used the in Memory (IM) column store in their source database?
- A. It must always transports existing INMEMORY attributes.
- B. It ignores the IM column store clause of the exporting objects.
- C. It always gives preference to the IM column store clause defined at the tablespace level over table-level definitions.
- D. Its TRANSFORM clause can be used to add the INMEMORV clause to exported tables that lack them.
- E. Its INMEM0RY_CLAUSE of the Data Pump Export allows modifications to IM column store clause of a table with existing INMEMORY setting.
- F. It can generates the INMEMORY clause that matches the table settings at export time.
正解:D、F
解説:
When importing objects that used the In-Memory (IM) column store in their source database using Oracle Data Pump, the following statements are true:
* D (Correct):TheTRANSFORMclause can be used to alter object creation DDL during import operations. This can include adding theINMEMORYclause to tables that were not originally using the IM column store.
* F (Correct):The import operation can preserve theINMEMORYattributes of tables as they were at the time of export, effectively replicating the IM column store settings from the source database.
The other statements are not accurate in the context of Data Pump import:
* A (Incorrect):Data Pump does not give preference to the IM column store clauses at the tablespace level over table-level definitions unless explicitly specified by theTRANSFORMclause.
* B (Incorrect):While Data Pump can transport existingINMEMORYattributes, it is not mandatory. It is controlled by theINCLUDEorEXCLUDEData Pump parameters or theTRANSFORMclause.
* C (Incorrect):TheINMEMORY_CLAUSEparameter is not part of the Data Pump Export utility. To modify the IM column store clauses, you would use theTRANSFORMparameter during import, not export.
* E (Incorrect):Data Pump does not ignore the IM column store clause unless specifically instructed to do so via theEXCLUDEparameter.
References:
* Oracle Database Utilities:Data Pump Export
* Oracle Database Utilities:Data Pump Import
質問 # 27
You need to collect and aggregate statistics for the ACCTG service and PAYROLL module, and execute:
Where do you find the output of this command?
- A. In the current working directory
- B. By viewing V$SERV_MOD_ACT_STATS
- C. In $ORACLE_BASE/diag/rdbms/<db unique name>/<instance name>/trace
- D. By viewing V$SERVICE_STATS
正解:B
解説:
When you enable statistics gathering for a specific service and module using DBMS_MONITOR.SERV_MOD_ACT_STAT_ENABLE, the output is aggregated and can be viewed using theV$SERV_MOD_ACT_STATSdynamic performance view. This view contains the cumulative statistics of database activity broken down by service and module, which is exactly what you collect when executing the provided command.
* B (Incorrect):While many types of trace files are located in the Diagnostic Destination directory (
$ORACLE_BASE/diag), the aggregated statistics for services and modules are not written to trace files but are instead viewable through dynamic performance views.
* C (Incorrect):TheV$SERVICE_STATSview provides service-level statistics but does not provide the
* combined service/module-level breakdown.
* D (Incorrect):The output of the PL/SQL block is not written to a file in the current working directory; it is stored in the data dictionary and accessible via dynamic performance views.
References:
* Oracle Database PL/SQL Packages and Types Reference:DBMS_MONITOR
* Oracle Database Reference:V$SERV_MOD_ACT_STATS
質問 # 28
Examine this code block, which executes successfully:
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?
- A. A warning alert will be issued only when CPU time exceeds 10000 microseconds for each user call.
- B. A critical alert will be issued when CPU time exceeds 2 minutes for each user call.
- C. A critical alert will be issued when CPU time exceeds 10000 microseconds for each user call.
- D. A warning alert will be issued when CPU time exceeds 1 minute for each user call.
正解:C
解説:
In the provided code block, theDBMS_SERVER_ALERT.SET_THRESHOLDprocedure 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 theSET_THRESHOLDprocedure are as follows:
* The first parameterDBMS_SERVER_ALERT.CPU_TIME_PER_CALLspecifies the metric for which the threshold is being set, in this case, the CPU time consumed per database call.
* The second and third parametersDBMS_SERVER_ALERT.OPERATOR_GEand'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 parametersDBMS_SERVER_ALERT.OPERATOR_GEand'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.
* 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.
References:
* Oracle Database 19c documentation on theDBMS_SERVER_ALERT.SET_THRESHOLDprocedure, 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.
質問 # 29
Examine this statement and output:
Which two situations can trigger this error?
- A. The capture directory is part of the root file system.
- B. The syntax is incomplete.
- C. The instance is unable to access the capture directory.
- D. The user lacks the required privileges to execute the DBMS WORKLOAD CAPTURE package or the directory.
- E. There is a file in the capture directory.
正解:C、D
解説:
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
質問 # 30
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. Create the KEEP cache and cache tables accessed by the SQL statements.
- B. Create the RECYCLE cache and cache tables accessed by the SQL statements.
- C. Increase the size of the library cache.
- D. Set OPTIMIZER_CAPTURE_SQL_PLAN_BASELINESto TRUE.
- E. Set the CURSOR_SHARING parameter to FORCE.
正解:C、E
解説:
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 theCURSOR_SHARINGparameter toFORCEwill 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):SettingOPTIMIZER_CAPTURE_SQL_PLAN_BASELINEStoTRUEcan 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
質問 # 31
Multiple sessions are inserting data concurrently into a table that has an LOB column.
At some point in time, one of the sessions cannot find available space in the LOB segment and needs to allocate a new extent.
Which wait event will be raised in the other sessions that need space in the LOB column?
- A. enq: SQ - contention
- B. enq: HW - contention
- C. enq: TM - contention
- D. enq: TX - allocate ITL entry
正解:B
解説:
When sessions concurrently insert data into a table with an LOB column and one session needs to allocate a new extent because it cannot find available space, the wait event associated with this contention is "enq: HW - contention". The HW stands for High Water Mark which is related to space allocation in the database segment.
When asession needs to allocate a new extent, it may raise this wait event in other sessions that are also attempting to allocate space in the same LOB segment.
References
* Oracle Database 19c Reference Guide - enq: HW - contention
質問 # 32
Which two statements are true about space usage in temporary tablespaces?
- A. When a global temporary table instantiation is too large to fit in memory, space is allocated in a temporary tablespace.
- B. When a session consumes all temporary tablespace storage, then the session would hang until the temporary space used by that session is cleared.
- C. A sort will fail if a sort to disk requires more disk space and no additional extent can be found/allocated in/for the sort segment.
- D. Lack of temporary tablespace space for sort operations can be prevented by using temporary tablespace groups.
- E. Temporary tablespaces setting Includes quotas to limit temporary space used by a session for that Temporary tablespace.
正解:A、D
解説:
Regarding space usage in temporary tablespaces, the following statements are true:
* A (Correct):When a global temporary table or a sort operation exceeds the available memory, Oracle Database allocates space in a temporary tablespace to store the temporary data or intermediate results.
* E (Correct):Using temporary tablespace groups can prevent insufficient temporary tablespace for sort operations by providing a collective pool of space from multiple temporary tablespaces, which can be used for user sorting operations.
The other options provided have inaccuracies:
* B (Incorrect):Oracle does not provide a mechanism for setting quotas on temporary tablespaces. Quotas can be set for permanent tablespaces but not for temporary ones.
* C (Incorrect):A sort operation may fail due to insufficient space, but Oracle will attempt to allocate space in the temporary tablespace dynamically. If no space can be allocated, an error is returned rather than a sort failure.
* D (Incorrect):If a session consumes all available temporary tablespace storage, Oracle will not hang the session; it will return an error to the session indicating that it has run out of temporary space.
References:
* Oracle Database Administrator's Guide:Managing Space for Schema Objects
* Oracle Database Concepts:Temporary Tablespaces
質問 # 33
Which three statements are true about server-generated alerts?
- A. Their threshold settings can be modified by using DBMS_SERVER_ALERT.
- B. They are logged in the alert log.
- C. They provide notifications but never any suggestions for correcting the identified problems.
- D. They can be viewed only from the Cloud Control Database home page.
- E. They are notifications from the Oracle Database Server of an existing or impending problem.
- F. They may contain suggestions for correcting the identified problems.
正解:B、E、F
解説:
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, usingDBMS_SERVER_ALERT, is not correct. Threshold settings are typically adjusted through Enterprise Manager or by modifying specific initialization parameters directly.
References:
* 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
質問 # 34
......
正真正銘のベスト試験材料1z1-084オンライン練習試験:https://jp.fast2test.com/1z1-084-premium-file.html