In a system, large online transaction processing (OLTP) jobs run during the daytime that require a
large database buffer cache. In the night, the system supports batch jobs that require a higher value
to be set for the large pool. You must simultaneously configure the memory components to
accommodate the peak requirement. What would you do to automate this configuration for the
memory components with change in mode of working?
A.
Set the SGA_TARGET initialization parameter to zero.
B.
Set the PRE_PAGE_SGA initialization parameter to TRUE.
C.
Set the MEMORY_MAX_TARGET initialization parameter to zero.
D.
Set the SGA_TARGET initialization parameter to a nonzero value.
SGA to non-zero value will be autotune the diferente SGA areas (db buffer and shared pool).
For daytime running large-scale online transaction processing (OLTP) operation (requires large buffer cache) and night run parallel batch jobs (requires a large pool of relatively large memory space) systems, you must configure the buffer cache and a large pool in order to accommodate peak demand.
With ASMM function, when OLTP job runs, gets most of the buffer cache memory to ensure good I / O performance.
When you start the data analysis and reporting batch job, the memory will automatically migrate to the large pool for the use of parallel query operations, but does not produce memory overflow error.
If you are using a server parameter file (SPFILE), the Oracle DB remembers automatically optimizes the size of the component every time you close an instance.
Therefore, the system does not need to have every time you start the instance again to understand the characteristics of the workload.
It can use information obtained from the previous example, the interruption of the last closed position from the beginning continue to assess the workload.
SGA_TARGET specifies the total size of all SGA components. If SGA_TARGET is specified, then the following memory pools are automatically sized:
Buffer cache (DB_CACHE_SIZE)
Shared pool (SHARED_POOL_SIZE)
Large pool (LARGE_POOL_SIZE)
Java pool (JAVA_POOL_SIZE)
Streams pool (STREAMS_POOL_SIZE)
If these automatically tuned memory pools are set to non-zero values, then those values are used as minimum levels by Automatic Shared Memory Management. You would set minimum values if an application component needs a minimum amount of memory to function properly.
The following pools are manually sized components and are not affected by Automatic Shared Memory Management:
Log buffer
Other buffer caches, such as KEEP, RECYCLE, and other block sizes
Fixed SGA and other internal allocations
SGA_TARGET to a nonzero value
The SGA_TARGET parameter can be set to a value that is less than or equal to the value of the SGA_MAX_SIZE initialization parameter. Set the value of the SGA_TARGET parameter to the amount of memory that you intend to dedicate to the SGA.
The system supports => So it’s System Global Area (SGA)