KEEP('APPOWNER.ADD_CLIENT','P');
Pinning of packages is more closely related to application management than application tuning,
but it can have a performance impact. If you can avoid dynamic management of fragmented
memory areas, you minimize the work Oracle has to do when managing the shared pool.
Specifying the Size of the SGA
To enable the automatic management of the caches, set the SGA_TARGET initialization parameter
to the size of the SGA.
If you choose to manage the caches manually, you can set the SGA_MAX_SIZE parameter to
the size of the SGA. You can then specify the sizes for the individual caches; they can be
dynamically altered while the database is running via the alter system command.
You can also set the SGA_TARGET to a size smaller than the SGA_MAX_SIZE. Oracle will use
the SGA_TARGET to initially set the individual caches and can grow them over time to occupy
more memory up to SGA_MAX_SIZE. This is a good way to determine what the total memory
requirements should be before deploying your database in a production environment.
Parameter Description
SGA_MAX_SIZE The maximum size to which the SGA can grow.
SHARED_POOL_SIZE The size of the shared pool.
DB_BLOCK_SIZE This will be the default database block size for the database.
DB_CACHE_SIZE The cache size specified in bytes.
DB_nK_CACHE_SIZE If you will be using multiple database block sizes within a single
database, you must specify at a DB_CACHE_SIZE parameter value and
at least one DB_nK_CACHE_SIZE parameter value.
Pages:
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431