I am working with a VS 2005 web application that I inherited. The app has a generic data access class to connect to either an Oracle or SQL Server backend. It is currently pointing to an Oracle 10g back-end.
Most data calls are dynamic sql statements build in strings and then passed to the data access class that returns an IDataReader object. Things were working well until we made some updates to the application and are now having regression errors.
The specific error, or lack of error, I am running into involves the OracleDBCommand's ExecuteReader method. When this method fires for a specific sql statement, no data is returned. If I step through the code and pull out the sql from the command, it will return data in my Oracle Developer window. A slightly varied statement (minus one where statement) works in both the app and Oracle Developer.
I tried changing the statement to use the OracleClient equivalents and the datareader worked just fine this time through.
Are there existing issues with the OleDbCommand and the ExecuteReader in connection with Oracle? Any ideas?
View Complete Post