The size of the shared pool is too small.
Cursors are not being shared.
A large number COMMITS are being performed.
There are frequent logons and logoffs.
The buffers are being read into the buffer cache, but some other session is changing the buffers.
第1题:
You notice a high number of waits for the db file scattered read and db file sequential read events in the recent Automatic Database Diagnostic Monitor (ADDM) report. After further investigation, you find that queries are performing too many full table scans and indexes are not being used even though the filter columns are indexed.Identify three possible reasons for this.()
A. Missing or stale histogram statistics
B. Undersized shared pool
C. High clustering factor for the indexes
D. High value for the DB_FILE_MULTIBLOCK_READ_COUNT parameter
E. Oversized buffer cache
第2题:
Examine the following parameters for a database instance: MEMORY_MAX_TARGET=0 MEMORY_TARGET=0 SGA_TARGET=0 PGA_AGGREGATE_TARGET=500m Which three initialization parameters are not controlled by Automatic Shared Memory Management (ASMM)?()
第3题:
Which statements are true regarding the system-defined moving window baseline in Oracle Database 11g?()
第4题:
You received complaints about the degradation of SQL query performance. You identified top SQL queries that consume time. What would be your next step to find out recommendations about statistics collection and restructuring of the SQL statement to improve query performance?()
第5题:
You notice a performance change in your production Oracle database and you want to know which change has made this performance difference. You generate the Compare Period Automatic Database Diagnostic Monitor (ADDM) report to further investigation. Which three findings would you get from the report?()
第6题:
The web Server ThreadsPerChild directive could be set too low.
The Web Container Thread Pool Minimum Size could be set too high.
The Web Container Thread Pool Maximum Size could be set too high.
The growable thread pool setting could be disabled for the Web Container.
第7题:
LOG_BUFFER
SORT_AREA_SIZE
JAVA_POOL_SIZE
STREAMS_POOL_SIZE
DB_16K_CACHE_SZIE
DB_KEEP_CACHE_SIZE
第8题:
The database instance is running with manual PGA management.
The database instance is running with manual shared memory management.
The database instance has the MEMORY_TARGET value set to a nonzero value.
All sessions are connected to the database instance in dedicated mode, and no RMAN or parallel queryoperations have been performed
第9题:
It detects any configuration change that caused a performance difference in both time periods.
It identifies any workload change that caused a performance difference in both time periods.
It detects the top wait events causing performance degradation.
It shows the resource usage for CPU, memory, and I/O in both time periods.
It shows the difference in the size of memory pools in both time periods.
It gives information about statistics collection in both time periods.
第10题:
The optimizer statistics are collected automatically.
Only the timed operating system (OS) statistics and plan execution statistics are collected.
The Oracle server dynamically generates the necessary statistics on tables as part of query optimization.
The snapshots for the Automatic Workload Repository (AWR) are not generated automatically.
Snapshots cannot be collected manually by using DBMS_WORKLOAD_REPOSITORY PACKAGE.
第11题:
LOG_BUFFER
DB_CACHE_SIZE
JAVA_POOL_SIZE
LARGE_POOL_SIZE
SHARED_POOL_SIZE
STREAMS_POOL_SIZE
第12题:
The collection level for the AWR should be set to BASIC
The moving window size must be less than Undo Retention
The moving window size should be greater than the Automatic Workload Repository (AWR) retention period
The moving window size should be equal to or less than the Automatic Workload Repository (AWR) retention period
第13题:
You plan to have a larger moving window size for the default system-defined moving window baseline because you want to use the adaptive threshold. Which statement factors in this consideration while increasing the size of the moving window?()
第14题:
View the Exhibit to examine the output produced by the following query at three different times since thedatabase instance started and has experienced workloads of different capacities:SQL> SELECT substr(component, 0, 10) COMP, current_size CS, user_specified_size US FROM v$memory_dynamic_componentsWHERE current_size!=0;What do you infer from this()
第15题:
You notice a high number of waits for the db file scattered read and db file sequential read events in the recent Automatic Database Diagnostic Monitor (ADDM) report. After further investigation, you find that queries are performing too many full table scans and indexes are not being used even though the filter columns are indexed. Identify three possible reasons for this.()
第16题:
You are configuring the PROD database to use an internal tuning algorithm to monitor the performance of the workload. To achieve this configuration, you specify the following parameter settings in the SPFILE:// SGA_TARGET = 512M SHARED_POOL_SIZE = 256M Which two statements are true when modifying the SHARED_POOL_SIZE initialization parameter in the SPFILE? ()
第17题:
Examine the details of the Top 5 Timed Events in the following Automatic Workloads Repository (AWR)report:What are three possible causes for the latch-related wait events?()
第18题:
The SGA_TARGET initialization parameter cannot be set to a value less than 1G
The SGA_TARGET initialization parameter cannot be set to a value greater than 1G
The Memory Advisor of the Oracle Enterprise Manager 10g cannot be used to obtain advice on the important memory components of the SGA
The values of the DB_CACHE_SIZE, SHARED_POOL_SIZE, LARGE_POOL_SIZE, and JAVA_POOL_SIZE initialization parameters cannot be set manually.
No minimum limits are imposed on the DB_CACHE_SIZE, SHARED_POOL_SIZE, LARGE_POOL_SIZE, and JAVA_POOL_SIZE initialization parameters.
The Automatic Shared Memory Management feature cannot be disabled unless you specify values for the DB_CACHE_SIZE, SHARED_POOL_SIZE, LARGE_POOL_SIZE, and JAVA_POOL_SIZE initialization parameters in the initialization parameter file.
第19题:
Modifying the SHARED_POOL_SIZE initialization parameter cannot be accomplished if the SGA_TARGET initialization parameter is set to a non-zero value.
Modifying the value of the SHARED_POOL_SIZE initialization parameter to zero is not allowed if the SGA_TARGET initialization parameter is set to a nonzero value.
Increasing the value of the SHARED_POOL_SIZE initialization parameter does not increase the shared pool component size. It sets the lower limit for the size of this component.
Decreasing the value of the SHARED_POOL_SIZE initialization parameter does not reduce the size of the shared pool component immediately. It sets the lower limit for the size of this component.
Increasing the value of the SHARED_POOL_SIZE initialization parameter immediately increases the shared pool component to the desired size by reallocating the additional memory from the auto-tuned memory components.
Decreasing the value of the SHARED_POOL_SIZE initialization parameter immediately shrinks the shared pool component to the desired size while reallocating the released memory to the memory components that are not auto-tuned.
第20题:
Missing or stale histogram statistics
Undersized shared pool
High clustering factor for the indexes
High value for the DB_FILE_MULTIBLOCK_READ_COUNT parameter
Oversized buffer cache
第21题:
It does not allow you to change the moving window size.
Adaptive threshold functionalities use it by default to compute statistics.
It is created by default with the window size being equal to the AWR retention time.
It is created when the first snapshot is collected by the Automatic Workload Repository (AWR).
第22题:
LOG_BUFFER
SORT_AREA_SIZE
JAVA_POOL_SIZE
STREAMS_POOL_SIZE
DB_16K_CACHE_SZIE
DB_KEEP_CACHE_SIZE
第23题:
The STATISTICS_LEVEL initialization parameter is set to BASIC
The PGA_AGGREGATE_TARGET initialization parameter is set to zero.
The SGA_MAX_SIZE initialization parameter is set to less than 20 GB
The DB_CACHE_SIZE initialization parameter is set to less than 5 GB
The SHARED_POOL_SIZE initialization parameter is set to a nonzero value.