10g performance issue

what is means of ADDM report

FINDING 1: 100% impact (111779 seconds)

---------------------------------------

Significant virtual memory paging was detected on the host operating system.

RECOMMENDATION 1: Host Configuration, 100% benefit (111779 seconds)

ACTION: Host operating system was experiencing significant paging but no

particular root cause could be detected. Investigate processes that

do not belong to this instance running on the host that are consuming

significant amount of virtual memory. Also consider adding more

physical memory to the host.

FINDING 2: 52% impact (57607 seconds)

-------------------------------------

Time spent on the CPU by the instance was responsible for a substantial part

of database time.

RECOMMENDATION 1: SQL Tuning, 28% benefit (31764 seconds)

ACTION: Tune the PL/SQL block with SQL_ID "10za58uy3uvhs". Refer to the

"Tuning PL/SQL Applications" chapter of Oracle's "PL/SQL User's Guide

and Reference"

RELEVANT OBJECT: SQL statement with SQL_ID 10za58uy3uvhs

Begin PKG_API_BUS.PRC_SEARCH_CASES(:v0, :v1, :v2, :v3, :v4, :v5, :v6,

:v7, :v8, :v9, :v10, :v11, :v12, :v13, :v14, :v15, :v16, :v17, :v18,

:v19, :v20, :v21, :v22, :v23, :v24, :v25, :v26, :v27, :v28, :v29,

:v30, :v31, :v32, :v33, :v34, :v35, :v36, :v37, :v38, :v39, :v40,

:v41, :v42, :v43, :v44, :v45, :v46, :v47, :v48, :v49, :v50, :v51,

:v52); End;

FINDING 4: 18% impact (20558 seconds)

-------------------------------------

The SGA was inadequately sized, causing additional I/O or hard parses.

RECOMMENDATION 1: DB Configuration, 6.5% benefit (7298 seconds)

ACTION: Increase the size of the SGA by setting the parameter

"sga_target" to 20480 M.

ADDITIONAL INFORMATION:

The value of parameter "sga_target" was "16384 M" during the analysis

period.

SYMPTOMS THAT LED TO THE FINDING:

SYMPTOM: Hard parsing of SQL statements was consuming significant

database time. (12% impact [13427 seconds])

SYMPTOM: Wait class "User I/O" was consuming significant database time.

(6.5% impact [7303 seconds])

FINDING 5: 11% impact (12417 seconds)

-------------------------------------

SQL statements were not shared due to the usage of literals. This resulted in

additional hard parses which were consuming significant database time.

RECOMMENDATION 1: Application Analysis, 11% benefit (12417 seconds)

ACTION: Investigate application logic for possible use of bind variables

instead of literals.

ACTION: Alternatively, you may set the parameter "cursor_sharing" to

"force".

RATIONALE: At least 616 SQL statements with PLAN_HASH_VALUE 2959524075

were found to be using literals. An example is SQL statement with

SQL_ID "56qt912zv01ru" .

RELEVANT OBJECT: SQL statement with SQL_ID 56qt912zv01ru and

PLAN_HASH 2959524075

SELECT VW_JO_Supreme_Appeal_Details.* FROM

VW_JO_Supreme_Appeal_Details WHERE UPPER(OPP_CASE_CODE) =

UPPER('0528600842021') Or UPPER(NEW_CASECODE) =

UPPER('0528600842021') ORDER BY ID DESC

RATIONALE: At least 616 SQL statements with PLAN_HASH_VALUE 2959524075

were found to be using literals. An example is SQL statement with

SQL_ID "fngk7u8wvr5d0" .

please lets me known if any one has knowledge of analysis ADDM Report