I'm sure there is a better space to post this, but I am new here, and have spent the last 20 minutes trying to find a better space, without success.
We have an application that uses .net to connect to an Oracle database.
We are using the opd.net 11.2 components to connect to our customers Oracle 11.2 database engine.
We can connect to the database, and execute SELECT queries and process the results without any issues, however we are having a problem with the UPDATE queries not actually altering the data in the table.
This is the query we are sending to the Oracle database engine.
BEGIN
UPDATE "STU_DUM_ACTIVE" SET "IS_READ" = '1' WHERE "STU_CODE" = '12345';
UPDATE "STU_DUM_ACTIVE" SET "GOT_PHOTO" = '1' WHERE "STU_CODE" = '12345';
COMMIT;
END;
For the record with "STU_CODE" = '12345', the "IS_READ" and "GOT_PHOTO" fields are a value of '0' before the UPDATE query runs. After the query runs through the opd.net application, the values are still '0', when we expect the values to be '1'.
The UPDATE query works in our application in our lab when executed against our test database, but on site, it is not working, and is not posting any errors to us to explain why it isn't working.
At this point, our customer is placing the blame squarely on us, and we need to come up with a solution, but I cannot see anything in the query that would cause an issue.
As supporting evidence for the customers claim that the issue is ours, they point to the fact that they can run the same query in the Oracle Developer application, and it updates the record just fine. So, I see their point, but I also know that the Oracle Developer doesn't use odp.net to connect to the database engine.
I'm hoping that somewhere there is a switch in Oracle that will disable UPDATES from odp.net or something of that nature that we can have them alter, and all will be good.
Any help would be appreciated.
Randall