Hello fellow experts,
We're having a problem with a client that's definitely puzzled me and I'm out of ideas.
We have an application developed using ASP classic that we normally use with SQL Server, but we do support Oracle 9i, it usually works fine even if we're not experts on Oracle but this week a client chose to migrate the system and it stopped working.
The workflow is pretty much the following:
2. Once the user finishes answering the test, the answers are saved in a "raw data" table, and sets the status as "not-processed". This works fine and the data is saved properly.
3. Here's where the tricky stuff starts to happen, after the raw answers are saved, ASP calls a (previously registered) DLL (written in VB6) to process the raw data and does two things:
3.1 Writes the "processed" values in a new table. (This fails)
3.2 AFTER 3.1, it sets the status as "processed" in the "raw data" table. (This works fine!, so the DLL is working OK)
So I have one theory, and that is that whatever is happening in the DLL isn't being commited (and never is), although UPDATES work fine.
The odd (or one of the odd) thing is that on the previous server with the "exact same" configuration (according to the client, I honestly don't believe it), the same system, same files, same everything worked OK.
I'm not sure if there's a way to configure Oracle 9i to commit all the time, maybe the Batch AutoCommit Mode on the ODBC? (we're using an old connection string and this just came to mind).
We even modifed the DLL and added the lines
And nothing happened.
More data: server is a Windows Server 2008, IIS 7, Oracle 9i.
Thanks in advance.