Database Tuning (MOSC)

MOSC Banner

Why is CURSOR_SHARING=FORCE not replacing literal values with binds

edited Apr 11, 2017 5:00AM in Database Tuning (MOSC) 12 commentsAnswered

I currently have cursor_sharing=force set; however, for some statements I still see literal values being passed. Shouldn't this parameter force a bind variable? It works for some statements, but not this one.

SQL> show parameter cursor_sharing

NAME     TYPE

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

VALUE

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

cursor_sharing     string

FORCE

Statement (from v$sqlarea):

SELECT apdata.*,service.name, staff.bookname as fname, store.name AS StoreName From ApData, Service, Staff, Store where Store.Store_Number = ApData.Store_Number AND  staff.id = apdata.staffid AND  service.id = apdata.serviceid AND  apdata.CustID = 812201 AND (apdata.Status < 3 OR apdata.Status > 4) AND apdata.ApID <> 114584010 AND apdata.StartTime > :V00005 ORDER BY apdata.StartTime

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center