Hello everyone!

Has anyone every seen the following behavior?

Oracle 9.? running on AIX, no problems here
Windows NT machine,
Oracle client installed on the NT machine with ODBC driver v 9.2.0.2

We have set up an ODBC source on the NT machine. An application (app
server) opens a connection pool with e.g. 4 read connections and 4 write
connections.

An application changes e.g. two rows in two different tables and commits.

The changed data is visible in TOAD from another machine.

After about 2 minutes, the data is reverted back to old values without
any activity from the app server whatsoever.

How is this possible? Note, this is definitely not a bug in the app
server code because the app runs without problems on 3 other Oracle
database installations and on many many other installations using
PostgreSQL, SQL Server and DB2. The app doesn't even know what the old
row values were!

Has anyone ever see something like this happening and how to solve it?

Thank you and best regards,

David

"DG" <info (AT) no-spam-e-resitve (DOT) com> wrote

Sounds like a rollback is being issued or the connection dies and a rollback
is done.

I would call support.
Jim

Jim Kennedy wrote:
The library commits using this function:

SQLRETURN SQLEndTran(
SQLSMALLINT HandleType,
SQLHANDLE Handle,
SQLSMALLINT CompletionType);

HandleType is SQL_HANDLE_DBC
CompletionType is SQL_COMMIT

Is committing using this function from ODBC lib not durable?

Can it happen that the committed data is visible in a parallel
connection/session and that at the same time the data can be rolled back
to the point before begin of transaction which was committed? If not,
then the changes shouldn't be visible in another transaction. I though
that if MVCC is used then the changed data will be visible only *after*
commit.

Best regards,

David