Note: This is INTERNAL ONLY research.  No action should be taken by the customer on this information.
This is research only, and may NOT be applicable to your specific situation.

KNOWLEDGE
-----------------
Keywords:  linux swap

1. Understanding and Tuning the Shared Pool and Tuning Library Cache Latch Contention (Doc ID 62143.1)
--NB: The shared pool itself should never be made so large that paging or swapping occur as performance can then decrease by many orders of magnitude.

2. Linux OS, Swapping and Databases (Doc ID 1295478.1)
--Make sure your total SGA, PGA fit in your RAM also leaving some decent memory for process spaces and system services. See the database installation guides for more information
--Consider using HugePages on Linux

3. HugePages on Oracle Linux 64-bit (Doc ID 361468.1)
--No Swapping: We must avoid swapping to happen on Linux OS at all Document 1295478.1. HugePages are not swappable (whereas regular pages are). Therefore there is no page replacement mechanism overhead. HugePages are universally regarded as pinned.

4. http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5/html/Oracle_Tuning_Guide/RHELTuningandOptimizationforOracleV11.pdf
--6.2. Checking Swap Space Size and Usage
--Swap usage may slowly increase as shown above but should stop at some point. If swap usage
--continues to grow steadily or is already large, then one of the following choices may need to be
--considered:
-- Adding more RAM.
-- Reducing the size of the SGA.
-- Increasing the size of the swap space.

note 1295478.1 and note 361468.1, implementing HugePages

provide us V$SQL_SHARED_CURSOR Report using (Doc ID 438755.1). This is very important

Your starting point is this doc 'HugePages on Oracle Linux 64-bit (Doc ID 361468.1)'. Read through it and through other Doc. Configure HugePages and let us know the result.

 3-3594462701