2.
The Shared Pool Administrator can be used to pin Oracle packages in the shared pool preventing them from being swapped out by Oracle.
There are two possible reasons for keeping a package permanently in the shared area:
- a package is large, so there is a risk that it won't fit back if it gets swapped out
- a package is often executed and swapping it out will increase the overhead
To be kept in the database, the package has to be loaded in the shared area.
The administrator window shows all the packages presently loaded,
so there is little point in running it unless the database has been running for a while.
Through the pop-up menu the packages can be sorted according to size or number of executions.
A Kept package will reside permanently in the shared pool until the Oracle restarts.
If the same packages are to be kept in the shared pool even after a restart,
a script that will load and pin those packages can be created from this tool.
This script should be run immediately after a database restart.
3.path:Installation/SQL File Executor
select pool, name,round(bytes/1024/1024) as mb from v$sgastat order by pool,mb desc
pool name mb
java pool free memory 32
shared pool free memory 332
shared pool sql area 6
shared pool miscellaneous 6
shared pool library cache 5
shared pool PL/SQL MPCODE 3
shared pool 1M buffer 2
shared pool PL/SQL DIANA 2
shared pool dictionary cache 2
shared pool KGLS heap 2
shared pool KQR M PO 1
shared pool message pool freequeue 1
shared pool KSXR receive buffers 1
shared pool KSXR pending messages que 1
shared pool event statistics per sess 1
4. init.ora
....
#######################
# Pools
#######################
java_pool_size =33554432
ared_pool_size =367001600
