Need suggestion for a topic in Oracle Call Interface

Question

Dear All,
I am kiran working as a TSE for EAI project.
I need a small clarification with respect to Oracle Call Interface.
My problem is as follows:
"I am doing a delete transaction in my application and not committing it, but when my program is killed externally, I observed that the transactions are being committed.
I thought it is a very strange behavior, as an aborted transaction should be rolled back.
But my PL told me that it the behavior OCI and got nothing to do with our application."                    
Now My question is, whether can we stop/(switch off) that auto commit option for OCI( Oracle Call Interface.
Awaiting for an earlier response.
Any kind of help is highly appreciated.
Thanks in advance,
Kiran

Answer 1

Here is some information from Oracle's documentation (Oracle Call Interface Programmer's Guide.
Commit or Rollback
An application commits changes to the database by calling OCITransCommit(). This call uses a service context as one of its parameters. The transaction is associated with the service context whose changes are committed. This transaction can be explicitly created by the application or implicitly created when the application modifies the database.
Note:
Using the OCI_COMMIT_ON_SUCCESS mode of the OCIExecute() call, the application can selectively commit transactions at the end of each statement execution, saving an extra round trip.
To roll back a transaction, use the OCITransRollback() call.
If an application disconnects from Oracle in some way other than a normal logoff, such as losing a network connection, and OCITransCommit() has not been called, all active transactions are rolled back automatically.