Is This Content Helpful?
We're glad to know this article was helpful.
Pinning database objects in Oracle's shared pool can improve database performance. It is recommended that all ESRI stored procedures and sequences be pinned. Once objects reside in Oracle's shared pool, they do not need to be parsed, which saves considerable resources.
Pinning objects in the shared pool uses available memory that might otherwise be used for other processes that share the pool. Allocate the additional memory to the shared pool as needed. In general, do not pin objects that are rarely used; this could have the adverse affect on database performance.
GRANT execute ON dbms_shared_pool TO sde;
EXECUTE dbms_shared_pool.keep ('STANDARD', 'P');
EXECUTE dbms_shared_pool.keep ('VERSION_UTIL', 'P');
EXECUTE dbms_shared_pool.keep ('LOCK_UTIL', 'P');
EXECUTE dbms_shared_pool.keep ('SDE.CONNECTION_ID_GENERATOR', 'Q');
Database objects have to be pinned after each instance startup, and ideally, immediately after the startup.
Portions of this article are from Oracle's Documentation. It is not intended to replace or supersede Oracle documentation. Please refer to Oracle documentation for additional information and further clarifications.