Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.misc -> VB3.0, ODBC, Oracle problems

VB3.0, ODBC, Oracle problems

From: Manuel Mall <mmnospam_at_arcus.com.au>
Date: 1 May 1998 13:22:33 GMT
Message-ID: <01bd74a7$6a71b840$0100a8c0@kant>


We have (what probably is already considered a "legacy") VB 3.0 application running under Win 3.11 that uses an Access MDB with attached tables from an Oracle database and observe two problems:

  1. One of the table contains a LONGVAR attribute to store large binary data. We observed that Windows occaisionally locks up when attempting to store larger files in that attribute. We are using the .New method followed by .AppendChunk to write that file to that attribute. These operations are working fine. It is the final .Update which appears to hang the machine.
  2. Of course, once the workstation hangs users reboot. However, it appears the old Oracle session is not killed on the server. As the operation which hung the workstation was executed within a database transaction the database locks are still in place and the Oracle database becomes unuseable (at least in parts) for other users. This must be a generic client/server database problem. If a client dies within a transaction there must be some means of terminating (=rollback) the transaction on the server. Anyone knows what the Oracle mechanisms in that case are?

Thanks

Manuel Received on Fri May 01 1998 - 08:22:33 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US