Cursor_sharing force partially parameter sql

Question

Hi ,
We are running our application with weblogic ,jdbc thin client with Oracle 9.2.0.5 database.
We have set cursor_sharing=FORCE in init.ora.
Our problem.
Java prepared statement with partial variable substitution is not sharing cursors, All other type of executions like update using sqlplus or without prepared statement they are sharing the cursors.
For example.
1)
UPDATE t1 SET col1=? WHERE id = 123
This gets translated into
UPDATE t1 SET col1= :1 WHERE nid = 123
where as
2)
UPDATE t1 SET col1=? WHERE id = ?
It gets translated into
UPDATE t1 SET col1= :1 WHERE nid = :2
We haved 1000 of update statements run in our application as example 1)
which is not sharing cursor.
Is there any parameter we can set in database?
This is happening in 9.2.0.6 also.

Answer 1

<quote>Is there any parameter we can set in database?</quote>
No.
And the behavior you describe actually makes sense. If you used bind variables where you considered it to be appropriate [and conversely, didn’t use them where it wasn’t appropriate], why would Oracle come in and override your decision by blindingly replacing all remaining literals with binds?
<quote>We haved 1000 of update statements run in our application as example 1) which is not sharing cursor.</quote>
Then those statements have to be re-written. CURSOR_SHARING=FORCE at the instance level is supposed to be a temporary band-aid anyway … the fix is to address the underlying coding problem and revert to CURSOR_SHARING=EXACT. Maybe, just maybe … have CURSOR_SHARING other than EXACT at session level surrounding some particular piece of code deemed too risky to re-code (3rd party, undocumented, too obscure) … but some regular UPDATEs? … just fix.