Parsing each time during execution

Question

Hi All,
I am just wondering why my sqls are parsed each time upon execution.
DB version :
select *From v$version;
BANNER
Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production
PL/SQL Release 11.2.0.2.0 - Production
CORE    11.2.0.2.0      Production
TNS for Linux: Version 11.2.0.2.0 - Production
NLSRTL Version 11.2.0.2.0 - ProductionI could see from TKPROF report that for each execution, i have one parse. This is for all sqls/dmls under this tkprof.
I have cursor_sharing set to EXACT and session_cached_cursors=50 (may be this is too low).
shared_pool_size=512 MB
cursor_space_for_time=FALSE
I have java application.
Is there any way i can have 1 time parse across multiple execution ?
SQL ID: cc5qh5gvfysby Plan Hash: 1237311609
SELECT BALANCE_CONTROL_VERSION,MATCH_SET_CLOSED_DATE,MATCH_KEY_ID,
  MATCH_SET_TYPE_ID,OPEN_BALANCE_UNIT,OPEN_BALANCE_VALUE,
  MATCH_SET_OPENED_DATE,RECORD_VERSION_NUMBER,MATCH_SET_STATE,
  TOTAL_BALANCE_UNIT,TOTAL_BALANCE_VALUE
FROM
MATCH_SETS WHERE MATCH_SET_ID=:1
call     count       cpu    elapsed       disk      query    current        rows
Parse     1555      0.08       0.06          0          0          0           0
Execute   1555      0.11       0.10          0          0          0           0
Fetch     1555      0.07       0.07          0       4710          0        1555
total     4665      0.28       0.24          0       4710          0        1555
Misses in library cache during parse: 1
Misses in library cache during execute: 1
Optimizer mode: ALL_ROWS
Parsing user id: 81 
Number of plan statistics captured: 3
SQL ID: gdy8k5wksn2zd Plan Hash: 0
INSERT INTO MATCH_SETS ( MATCH_SET_ID,BALANCE_CONTROL_VERSION,
  MATCH_SET_CLOSED_DATE,MATCH_KEY_ID,MATCH_SET_TYPE_ID,OPEN_BALANCE_UNIT,
  OPEN_BALANCE_VALUE,MATCH_SET_OPENED_DATE,MATCH_SET_STATE,TOTAL_BALANCE_UNIT,
  TOTAL_BALANCE_VALUE )
VALUES
(:1,:2,:3,:4,:5,:6,:7,:8,:9,:10,:11)
call     count       cpu    elapsed       disk      query    current        rows
Parse      523      0.01       0.02          0          0          0           0
Execute    523      0.38       0.50         58        920       6764         523
Fetch        0      0.00       0.00          0          0          0           0
total     1046      0.40       0.52         58        920       6764         523
Misses in library cache during parse: 1
Misses in library cache during execute: 1
Optimizer mode: ALL_ROWS
Parsing user id: 81 
Number of plan statistics captured: 3

Answer 1

Hi,
I don't see parsing problem in your post.
The select statement has 1555 parses out of which 1 missed in library cache.
The insert statement has 523 parses with 1 library cache miss.
What you really want to check is the "soft parse" and "hard parse" statistics for your session.
An idea to check that is to enable AUTOTRACE in SQL*Plus and execute the select statement over there and check the statistics.
Good luck.