Good idea. Cursor_Sharing = force results in the SQL statements being converted, substituting the hard-coded values with temporary bind variables before they are parsed.
It helps where the SQL problem is a scarcity of bind variables, but that is probably not the only coding problem that contributes to your miseries(bet they never heard of joins, outer, inner or multidimensional??).
From: John Lewis [mailto:[EMAIL PROTECTED]]
Sent: Thursday, September 06, 2001 6:30 PM
To: Multiple recipients of list ORACLE-L
Subject: RE: Egregious coding
-----Original Message-----
From: Hagedorn, Linda [mailto:[EMAIL PROTECTED]]
Sent: Thursday, September 06, 2001 4:06 PM
To: Multiple recipients of list ORACLE-L
Subject: Egregious coding
Has anyone thought of a clever way to fail every SQL statement that does not use a bind variable that I could switch on and off as required?
I'm looking at hundreds of thousands of queries in the v$sqlarea in production. I've taken engineering management to task over this, and have gotten empty promises in return. I would love to hold a valid threat over their heads that I'm going to shut off every statement that is not coded properly.
Any ideas are appreciated.
Linda
