This content has been marked as final. Show 6 replies
Commit_Confirm is not autocommitting the insert it is to guarantee a ditributed transaction. What you need is an isert like single_site_autocommit and this feature is available only in Database Gateway for ODBC 11.2 - the follow up product of hsodbc.
D4ODBC 11.2 is certified with an Oracle database release 10.2.4 and 10.2.0.5.
Sorry, I forgot to say the Gateway version. It's 184.108.40.206.0, so it could not work because the database version is not certified?
I'll try the single_site_autocommit, I thougth I needed commit_confirm.
Yes, your RDBMS needs to be at 10.2.0.4 or 10.2.0.5 to work fully with 11.2 DG4ODBC. It may work at lower versions but you will get unpredictable problems or results.
For details of using the parameter -
have a look at this note in My Oracle Support -
Oracle Database Gateways (DG4MSQL, DG4DRDA, DG4SYBS, DG4TERA, DG4IFMX, DG4ODBC) and Locking on Non-Oracle Databases (Doc ID 1380465.1)
But I would like to be capable of rolling back and the SINGLE_SITE_AUTOCOMMIT makes an auto commit after each statement,
so it's not useful for my purpose.
I thought that the COMMIT_CONFIRM value would be the solution.
Commit_Confirm is for distributed transactions and this kind of insert is locking the remote table once you insert/update/delete a row in the foreign database
So the only way for parallel inserts into a foreign database is using autocommit.
So I can't do simultaneous updates to the foxpro tables.
Thanks for your helpl.