Low Execute to Parse % and high soft parse %

Question

Hello Folks
I am working on oracle 10g release2 on HP-UX
After going through awr reports observed it have low Execute to Parse % but high soft parse % (Instance Efficiency Percentages)
so cannot say issue with less use of bind variables,then what is cause of Execute to Parse %
searched sites like ask.tom,burselon counsulting etc as usual they had given generic/diplomatic(escaping) replies on this
like due to problem in application code,ineffecient sharing ,due to problem in database parameters etc
without any clear indication for cause and solution like if some database parameters not set properly then should say which database parameters can be checked,cause due to more parsing and less execution
please share if you had faced such issue and any suggestions to solve this
examples why this could happen ,like possibilities in application code
Thanks

Answer 1

  Load Profile
                                          Per Second       Per Transaction
               Redo size:             11,685.79              3,660.98
               Logical reads:             71,445.74             22,382.86
               Block changes:                 70.89                 22.21
               Physical reads:                 58.63                 18.37
               Physical writes:                  2.80                  0.88
               User calls:                652.93                204.55
               Parses:                 48.39                 15.16
               Hard parses:                  0.33                  0.10
               Sorts:                  6.90                  2.16
               Logons:                  0.23                  0.07
               Executes:                 52.71                 16.51
               Transactions:                  3.19
            % Blocks changed per Read:    0.10    Recursive Call %:    30.48
            Rollback per transaction %:    2.57       Rows per Sort:    29.66
    Instance Efficiency Percentages (Target 100%)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
             Buffer Nowait %:  100.00       Redo NoWait %:  100.00
             Buffer  Hit   %:   99.92    In-memory Sort %:  100.00
             Library Hit   %:   98.47        Soft Parse %:   99.32
             Execute to Parse %:    8.19         Latch Hit %:   99.63
             Parse CPU to Parse Elapsd %:   89.90     % Non-Parse CPU:   99.62There rdbms performs approximately 48 soft parse per second ,Soft Parse % and Library Hit very close to 99 it means there main part of sql are shared.Also here user calls similar high per second but executions less,however you should be try minimizing soft parsing.I do not know exactly for which interval you get this report but Execute to Parse % indicate that when executing query oracle can not find early cursor handles(open or closed) but it can find sql text and plan information from shared pool according hash values,in this case oracle perform soft parse again.In your case you also investigate shared pool size/fragmentation.To avoid little Execute to Parse % you can increase SESSION_CACHED_CURSORS or implement CURSOR_SPACE_FOR_TIME.So refer documentation and find how to use these parameters.