• ホーム
  • ブログ
  • 1z1-084試験問題集合格させるのは2025年最新の認証済み試験問題 [Q13-Q31]

1z1-084試験問題集合格させるのは2025年最新の認証済み試験問題 [Q13-Q31]

Share

1z1-084試験問題集合格させるのは2025年最新の認証済み試験問題

1z1-084試験問題でリアルに更新された問題PDF


オラクル1Z0-084認定試験は、Oracle Database 19cのパフォーマンス管理に深い理解を持つことを求める上級レベルの試験です。候補者は、さまざまなパフォーマンスチューニング技術を経験し、パフォーマンスを監視・管理するために使用されるツールやユーティリティに精通している必要があります。また、パフォーマンスの問題をトラブルシューティングし、データベースを最大効率で最適化する能力を持っている必要があります。

 

質問 # 13
Which two statements are true about cursor sharing?

  • A. Setting Cursor_sharing to FORCE can result in a plan that is suboptimal for the majority of values bound to a bind variable when executing a cursor with one or more bind variables.
  • B. Adaptive Cursor Sharing requires histograms on filtered columns, used in equality predicates, to allow different execution plans to be generated for statements whose bound values would normally generate different plans at hard parse time.
  • C. Adaptive Cursor Sharing guarantees that a suboptimal plan will never be used on any execution of a SQL statement.
  • D. Setting cursor_sharing to EXACT prevents Adaptive Cursor Sharing from being used.
  • E. Setting optimizer_capture_sql_plan_baselines to TRUE loads all adaptive plans for the same statement into the cursor cache.

正解：A、D

解説：
A: WhenCursor_sharingis set toFORCE, Oracle tries to avoid hard parses by replacing literals in SQL statements with bind variables, even if the original statement didn't include bind variables. This can lead to the use of a single execution plan for multiple executions of a statement with different literal values, which might not be optimal for all executions.
D: Settingcursor_sharingtoEXACTensures that SQL statements must match exactly for them to share a cursor. This setting prevents the use of Adaptive Cursor Sharing (ACS) since ACS relies on the ability to share cursors among similar statements that differ only in their literal values. WithEXACT, there's no cursor sharing for statements with different literals, hence no opportunity for ACS to operate.
References:
* Oracle Database SQL Tuning Guide, 19c
* Oracle Database Reference, 19c


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

  • A. COLUMN STORE COMPRESS FOR QUERY HIGH
  • B. ROW STORE COMPRESS ADVANCED
  • C. MN STORE COMPRESS FOR QUERY LOW
  • D. STORE COMPRESS

正解：A

解説：
The question asks to reduce database I/O impact without increasing the buffer cache size or modifying SQL statements. This indicates a need to reduce the physical I/O required to access the data. Let's analyze the scenario and the options.
Analysis of the AWR Report:
* Top Wait Events:
* The top foreground wait event is db file sequential read, which accounts for 40.4% of DB time.
This indicates significant physical I/O operations, primarily single-block reads, which are typically associated with index access.
* Reducing the physical I/O associated with db file sequential read can significantly improve performance.
* SQL Ordered by Reads:
* The SQL consuming the most reads involves high physical I/O. This confirms the need to reduce I
/O overhead by compressing data efficiently to minimize physical reads.
Compression Techniques and Their Suitability:
* A. COLUMN STORE COMPRESS FOR QUERY LOW:
* This option is a columnar compression method that optimizes for query performance but provides less compression compared to the HIGH option. While effective, it is not as suitable as FOR QUERY HIGH for reducing I/O.
* B. STORE COMPRESS:
* This is the basic compression option for tables and does not offer the advanced capabilities required for reducing significant physical I/O for queries.
* C. ROW STORE COMPRESS ADVANCED:
* This is a row-level compression that is suitable for OLTP workloads. While it reduces storage, it does not reduce query-related I/O as effectively as columnar compression.
* D. COLUMN STORE COMPRESS FOR QUERY HIGH (Correct Option):
* This is the most effective option for reducing query-related I/O. It:
* Uses columnar compression to reduce the size of data stored on disk.
* Reduces the number of physical reads by compressing data highly, meaning fewer blocks need to be read.
* Optimizes query performance for analytical workloads, which aligns with the scenario described in the AWR report.
Why COLUMN STORE COMPRESS FOR QUERY HIGH Is the Best Fit:
* It is designed to improve query performance by minimizing the amount of I/O required.
* Suitable for environments with heavy read operations (as indicated by the db file sequential read waits).
* Does not require changes to SQL or buffer cache size, adhering to the constraints in the question.
Reference to Oracle Documentation:
* Oracle Database 19c Performance Tuning Guide:
* Section: Using Compression to Reduce Storage and I/O Requirements.
* Discussion of columnar compression techniques for reducing I/O in query-intensive environments.
* Oracle Advanced Compression Documentation:
* Details on COLUMN STORE COMPRESS FOR QUERY HIGH and its benefits for analytical workloads.


質問 # 15
Examine this statement and output:

Which three statements are true?

  • A. Session 9822 will always stop waiting if the session that owns the TX enqueue issues a COMMIT statement as session 9822 is the first session in the transaction queue.
  • B. Session 9857 waited 1354 seconds for another process, which was also waiting for a transaction to end.
  • C. Session 8779 may be waiting for a user or application response.
  • D. Session 9857 is not waiting.
  • E. Both 9822 and 8779 sessions are waiting for operating system resources.
  • F. Session 8779 may be waiting due to a network problem.

正解：A、C、F

解説：
For this SQL statement and output, we can analyze the EVENT column to understand the type of wait:
B: The event "SQL*Net message from client" typically indicates that the session is waiting for a response from the client. This can be due to a network issue, user response, or an application processing delay.
E: The event "SQL*Net message from client" also implies that the session is idle waiting for the client (a user or an application) to send a request to the server. This event usually indicates that the session is not actively working but is instead waiting for the next command.
F: The wait event "enq: TX - row lock contention" suggests that session 9822 is waiting for a row-level lock held by another session. If the holding session issues a COMMIT or ROLLBACK, the lock will be released, and session 9822 will stop waiting. Since this session is experiencing row lock contention, it implies it's waiting for a specific transaction to complete.
References:
* Oracle Database Reference, 19c
* Oracle Wait Events Documentation


質問 # 16
Examine these commands, which execute successfully:

Which statement is true?

  • A. AD DM is enabled for all pluggable databases.
  • B. ADDM, AWR, and ASH reports can be purged automatically.
  • C. AWR snapshots can be purged manually in pluggable databases.
  • D. AWR- snapshots in all pluggable databases will be purged automatically after every 60 mins.

正解：C

解説：
The DBMS_WORKLOAD_REPOSITORY.MODIFY_SNAPSHOT_SETTINGS procedure allows
setting attributes related to AWR snapshots. While the interval setting controls the frequency of snapshot generation, purging them is a separate process that can be managed either automatically (with retention settings) or manually.References:
* Oracle Database PL/SQL Packages and Types Reference, 19c
* Oracle Multitenant Administrator's Guide, 19c


質問 # 17
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. reducing the values of DB_FILE_MULTILOCK_READ_COUNT to 64
  • B. increasing the value of DBWRITERPROCESSES to 64,
  • C. setting dbwr_io_slaves to 64
  • D. increasing the value of DB_FILE_MULTIBLOCK_READ_COUNT to 128
  • E. Increasing the size of MEMORYTARGET

正解：B、C

解説：
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 the DBWR_IO_SLAVES parameter 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 of DBWRITERPROCESSES enables 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


質問 # 18
Examine this statement and output:

Which two situations can trigger this error?

  • A. The instance is unable to access the capture directory.
  • B. The syntax is incomplete.
  • 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. There is a file in the capture directory.

正解：A、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


質問 # 19
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 can generates the INMEMORY clause that matches the table settings at export time.
  • B. It must always transports existing INMEMORY attributes.
  • C. Its INMEM0RY_CLAUSE of the Data Pump Export allows modifications to IM column store clause of a table with existing INMEMORY setting.
  • D. It ignores the IM column store clause of the exporting objects.
  • E. Its TRANSFORM clause can be used to add the INMEMORV clause to exported tables that lack them.
  • F. It always gives preference to the IM column store clause defined at the tablespace level over table-level definitions.

正解：A、E

解説：
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


質問 # 20
Examine this statement and its corresponding execution plan:

Which phase introduces the CONCATENATION step?

  • A. SQL Semantic Check
  • B. SQL Transformation
  • C. SQL Row Source Generation
  • D. SQL Execution
  • E. SQL Adaptive Execution

正解：B

解説：
The CONCATENATION step in an execution plan is introduced during the SQL Transformation phase. This phase is part of the optimizer's query transformations which can include various techniques to rewrite the query for more efficient execution. The CONCATENATION operation is used to combine the results of two separate SQL operations, typically when there is an OR condition in the WHERE clause, as seen in the provided query.
References:
* Oracle Database SQL Tuning Guide, 19c
* Oracle Database Concepts, 19c


質問 # 21
You are informed that the RMAN session that is performing the database duplication is much slower than usual. You want to know the approximate time when the rman operation will be completed.
Which view has this information?

  • A. V$SESSION_LONGOPS
  • B. V$RMAN_BACKUP_JOB_DETAILS
  • C. V$SESSION
  • D. V$SESSTAT

正解：A

解説：
In Oracle Database, theV$SESSION_LONGOPSview provides insights into various operations within the database that are expected to take more than six seconds to complete. These include operations related to RMAN (Recovery Manager), such as database duplication tasks. This view displays information about the progress of these long-running operations, including the start time, elapsed time, and estimated time to completion.
When an RMAN session is performing a database duplication and is observed to be slower than usual, checking theV$SESSION_LONGOPSview can give an approximation ofwhen the RMAN operation might complete. This view includes fields likeTIME_REMAININGandELAPSED_SECONDSthat help in estimating the completion time of the operation based on its current progress.
References:
* Oracle Database Reference:V$SESSION_LONGOPS
* Oracle Database Backup and Recovery User's Guide:Monitoring RMAN Jobs


質問 # 22
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. By viewing V$SERV_MOD_ACT_STATS
  • B. By viewing V$SERVICE_STATS
  • C. In $ORACLE_BASE/diag/rdbms/<db unique name>/<instance name>/trace
  • D. In the current working directory

正解：A

解説：
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


質問 # 23
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. By viewing V$SERV_MOD_ACT_STATS
  • B. By viewing V$SERVICE_STATS
  • C. In $ORACLE_BASE/diag/rdbms/<db unique name>/<instance name>/trace
  • D. In the current working directory

正解：A

解説：
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 the V$SERV_MOD_ACT_STATS dynamic 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): The V$SERVICE_STATS view 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


質問 # 24
Which three statements are true about using the in Memory (IM) column store?

  • A. It does not improve performance for queries using cached results of function evaluations on columns from the same table.
  • B. It does not improve performance for queries using user-defined virtual column results.
  • C. It does not require all database data to fit in memory to improve query performance.
  • D. It does not improve performance for queries that use join groups on columns from different tables.
  • E. It can improve OLTP workload performance by avoiding the use of indexes.
  • F. It improves performance for queries joining several tables using bloom filter joins.

正解：C、E、F

解説：
The Oracle In-Memory (IM) column store feature enhances the performance of databases by providing a fast columnar storage format for analytical workloads while also potentially benefiting OLTP workloads.
* C (True): It can improve OLTP workload performance by providing a faster access path for full table scans and reducing the need for indexes in certain scenarios, as the In-Memory store allows for efficient in-memory scans.
* E (True): The In-Memory column store does not require all database data to fit in memory. It can be used selectively for performance-critical tables or partitions, and Oracle Database will manage the population and eviction of data as needed.
* F (True): In-Memory column store can significantly improve performance for queries joining several tables, especially when bloom filters are used, as they are highly efficient with the columnar format for large scans and join processing.
The other options provided are not correct in the context of the In-Memory column store:
* A (False): While In-Memory column store is designed for analytical queries rather than caching results of function evaluations, it does not specifically avoid improving performance for queries using cached results of function evaluations.
* B (False): In-Memory column store can improve the performance of queries that use join groups, which can be used to optimize joins on columns from different tables.
* D (False): In-Memory column store can improve the performance of queries using expressions, including user-defined virtual columns, because it supports expression statistics which help in optimizing such queries.
References:
* Oracle Database In-Memory Guide: In-Memory Column Store in Oracle Database
* Oracle Database In-Memory Guide: In-Memory Joins
* Oracle Database In-Memory Guide: In-Memory Aggregation


質問 # 25
Database performance has degraded recently.
index range scan operations on index ix_sales_time_id are slower due to an increase in buffer gets on sales table blocks.
Examine these attributes displayed by querying DBA_TABLES:

Now, examine these attributes displayed by querying DBA_INDEXES:

Which action will reduce the excessive buffer gets?

  • A. Partition index IX_SALES_TIME_ID using hash partitioning.
  • B. Re-create the SALES table using the columns in IX_SALES_TIME_ID as the hash partitioning key.
  • C. Re-create the SALES table sorted in order of index IX_SALES_TIME_ID.
  • D. Re-create index IX_SALES_TIME_ID using ADVANCED COMPRESSION.

正解：D

解説：
Given that index range scan operations on IX_SALES_TIME_ID are slower due to an increase in buffer gets, the aim is to improve the efficiency of the index access. In this scenario:
* B (Correct): Re-creating the index using ADVANCED COMPRESSION can reduce the size of the index, which can lead to fewer physical reads (reduced I/O) and buffer gets when the index is accessed, as more of the index can fit into memory.
The other options would not be appropriate because:
* A (Incorrect): Re-creating the SALES table sorted in order of the index might not address the issue of excessive buffer gets. Sorting the table would not improve the efficiency of the index itself.
* C (Incorrect): Using the columns in IX_SALES_TIME_ID as a hash partitioning key for the SALES table is more relevant to data distribution and does not necessarily improve index scan performance.
* D (Incorrect): Hash partitioning the index is generally used to improve the scan performance in a parallel query environment, but it may not reduce the number of buffer gets in a single-threaded query environment.
References:
* Oracle Database SQL Tuning Guide: Managing Indexes
* Oracle Database SQL Tuning Guide: Index Compression


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

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

正解：A、C

解説：
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
Which two Oracle Database features use database services?

  • A. Oracle SQL Performance Management
  • B. Database Resource Manager
  • C. Oracle Scheduler
  • D. Oracle Automatic Reoptimization
  • E. Oracle SQL Tuning Advisor

正解：B、C

解説：
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


質問 # 28
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. Increase the size of the library cache.
  • B. Create the RECYCLE cache and cache tables accessed by the SQL statements.
  • C. Set the CURSOR_SHARING parameter to FORCE.
  • D. Set OPTIMIZER_CAPTURE_SQL_PLAN_BASELINESto TRUE.
  • E. Create the KEEP 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 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


質問 # 29
Which two statements are true about space usage in temporary tablespaces?

  • A. When a session consumes all temporary tablespace storage, then the session would hang until the temporary space used by that session is cleared.
  • B. Lack of temporary tablespace space for sort operations can be prevented by using temporary tablespace groups.
  • C. When a global temporary table instantiation is too large to fit in memory, space is allocated in a temporary tablespace.
  • D. Temporary tablespaces setting Includes quotas to limit temporary space used by a session for that Temporary tablespace.
  • E. 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.

正解：B、C

解説：
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


質問 # 30
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 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.
  • 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 expdp from the ftatspack 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 AWR repository.

正解：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 the exp utility 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): expdp is not designed to export from Statspack, and awrload is intended for loading from an AWR export file, not a Statspack export.
* B (Incorrect): Although expdp and impdp are 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): Using expdp to 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


質問 # 31
......

合格させる保証付き無料クイズ2025年最新の実際に出ると確認されたOracle：https://www.passtest.jp/Oracle/1z1-084-shiken.html

無料Oracle Database 19c 1z1-084究極の学習ガイド：https://drive.google.com/open?id=1Vx3rh9TgP5a2V-h2-r6jETfd-z6crp8n

関するブログ

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