[Free] 2018(Jan) EnsurePass Testinsides Oracle 1z0-053 Dumps with VCE and PDF 471-480
Oracle Database 11g: Administration II
Question No: 471 – (Topic 14)
View the Exhibit to observe the error.
You receive this error regularly and have to shutdown the database instance to overcome the error. Automatic Shared Memory Management is configured for the instance.
What can you do to reduce the chance of this error in the future?
Increase the value of SGA_MAX_SIZE
Enable automatic memory management
Set the PRE_PAGE_SGA parameter to true
Lock the System Global Area (SGA) in memory
Answer: B Explanation:
ORA-04031: unable to allocate string bytes of shared memory (quot;stringquot;,quot;stringquot;,quot;stringquot;,quot;stringquot;)
Cause: More shared memory is needed than was allocated in the shared pool or Streams pool.
Action: If the shared pool is out of memory, either use the DBMS_SHARED_POOL package to pin large packages, reduce your use of shared memory, or increase the amount of available shared memory by increasing the value of the initialization parameters SHARED_POOL_RESERVED_SIZE and SHARED_POOL_SIZE. If the large pool is out of memory, increase the initialization parameter LARGE_POOL_SIZE. If the error is issued from an Oracle Streams or XStream process, increase the initialization parameter STREAMS_POOL_SIZE or increase the capture or apply parameter MAX_SGA_SIZE.
Question No: 472 – (Topic 14)
In your database, the RESULT_CACHE_MODE parameter has been set to MANUAL in the initialization parameter file. You issued the following command:
SQLgt;SELECT /* RESULT_CACHE */ sale_category, sum(sale_amt) FROM sales GROUP BY sale_category;
Where would the result of this query be stored?
database buffer cache
Question No: 473 – (Topic 14)
Automatic PGA Memory Management eliminates the need to manually configure which of the following initialization parameters? (Choose all that apply.)
Question No: 474 – (Topic 14)
When tuning Automatic PGA Memory Management, which of the following views will provide the information specified?
The V$PGA_TARGET_ADVICE view shows the predicted cache hit-ratio improvement if you increase PGA_AGGREGATE_TARGET.
The V$PGA_TARGET_ADVICE view shows how the V$SQL_WORKAREA histogram will change if you change the value of PGA_AGGREGATE_TARGET.
The V$PGA_TARGET_ADVICE_HISTOGRAM view shows how the V$SQL_WORKAREA_HISTOGRAM will change if you switch between Manual and Automatic PGA Memory Management.
The V$PGA_TARGET_ADVICE view shows how performance will improve for the different work areas if you switch from Manual to Automatic PGA Memory Management.
Question No: 475 – (Topic 14)
View the Exhibit to examine the output produced by the following query at three different times since the database instance started and has undergone workloads of different capacities:
SQLgt; SELECT substr(component, 0, 10) COMP, current_size CS, user_specified_size US FROM v$memory_dynamic_components
WHERE current_size!=0; What do you infer from this? Exhibit:
All sessions are connected to the database instance in dedicated mode, and no RMAN or parallel query operations have been performed.
The database instance is running with manual shared memory management.
The database instance is running with manual PGA management.
The database instance has the MEMORY_TARGET value set to a nonzero value.
Question No: 476 – (Topic 14)
View the Exhibit to examine the parameter values. You are planning to set the value for the MEMORY_TARGET parameter of your database instance.
What value would you assign? Exhibit:
Question No: 477 – (Topic 14)
View the Exhibit and examine the parameter settings in your server-side parameter file (SPFILE). When you tried to start the database instance, you received the following error:
ORA-00824: cannot set SGA_TARGET or MEMORY_TARGET due to existing internal settings, see alert log for more information
Why did the instance fail to start? Exhibit:
Because the PGA_AGGREGATE_TARGET parameter is not set
Because the STATISTICS_LEVEL parameter is set to BASIC
Because MEMORY_TARGET and MEMORY_MAX_TARGET cannot be equal
Because both the SGA_TARGET and MEMORY_TARGET parameters are set.
Answer: B Explanation:
Setting SGA Target Size
You enable the automatic shared memory management feature by setting the SGA_TARGET parameter to a nonzero value. This parameter sets the total size of the SGA. It replaces the parameters that control the memory allocated for a specific set of individual components, which are now automatically and dynamically resized (tuned) as needed.
The STATISTICS_LEVEL initialization parameter must be set to TYPICAL (the default) or ALL for automatic shared memory management to function.
Question No: 478 – (Topic 14)
You have applications that have frequently executed queries, and produce small and static result sets. You configure the sqlnet.ora file in the client machine to set a nonzero value for the OCI_RESULT_CACHE_MAX_SIZE parameter.
What is the purpose of this configuration?
to avoid round trips to the server by enabling caching of query results in client memory
to improve performance by storing a copy of the data from the private SQL area of the PGA
to enhance the query performance by creating a cache in the client memory for sorting operations
to avoid the storing of query plans and results in the server by creating a cache in the client memory
Question No: 479 – (Topic 14)
Which statements about the MEMORY_TARGET initialization parameter are true? (Choose all that apply.)
MEMORY_TARGET can be increased up to the value of MEMORY_MAX_TARGET, if MEMORY_MAX_TARGET is set to a value greater than zero
MEMORY_MAX_TARGET defaults to a value of zero if MEMORY_TARGET is not set
MEMORY_TARGET represents the total amount of memory that can be allocated to SGA and PGA memory structures.
MEMORY_TARGET is static and cannot be modified without shutting down the instance
Question No: 480 – (Topic 14)
Note the following parameters settings in your database:
You issued the following command to increase the value of DB_8K_CACHE_SIZE: SQLgt; ALTER SYSTEM SET DB_8K_CACHE_SIZE=140M;
What would happen?
It will fail because DB_8K_CACHE_SIZE parameter cannot be changed dynamically
It will be successful only if the memory is available from the auto tuned components
It will fail because an increase in DB_8K_CACHE_SIZE cannot be accommodated within SGA_TARGET
It will fail because an increase in the DB_8K_CACHE_SIZE cannot be accommodated within
Answer: D Explanation:
This is an actually mathematic question.
|Lowest Price Guarantee||Yes||No||No|
|Free VCE Simulator||Yes||No||No|