Is There a Problem with "ocon" (autocommit) in OCI?

Hi Folks,

I've been using a locally-written C++ OCI library which calls "ocon" as soon as a database connection is established, to autocommit all transactions. This seemed to work well until the applications exceeded a certain size and complexity. My most recent implementation is a fairly large application which does a lot of comparisons, insert/deletions, and updates; it takes several hours to run on an HP 9000/827 database server.

This hoggy application began returning ORA-1555 "Snapshot too Old" errors after 1 to 2 hours, causing the application to fail. Making RBSBIG the primary rollback segment had no noticeable affect.

While pursuing various guesses I recently commented out the call to ocon, and put explicit commits (ocom) in the application at longer processing intervals. Since then, the problem with the snapshot errors has disappeared.

Does anyone know of a problem relating to the use of ocon? We're using Oracle7 Server Release 7.1.6.2.0 on an HPUX A.09.04 E system. I'm trying to find out if this is a "random recompile fix" or if there really is a good reason to avoid using ocon.

Thanks for any help.

                                           Scott Chilcote
                                           scotty_at_pagesz.net

-- 
,____________________________________________________________________________,
||Disclaimer: These opinions / LINUX:\\    "/^\|^\ /\  |\ /|   is not a     ||
|| are my own.  Sales have //  Where  \\    `-.|_//__\ | V |    family      ||
|| been down lately.     // Freedom Isn't\\ \_/| /    \|   |    value!"     ||


`-------------------------==> Virtual! <==-----------------------------------'