Re: HELP: Long (lasting) transactions?

In article <3makt8$sv@hustle.rahul.net>, billb@lore.kla.com (Bill Baloglu) says: > >We are designing a C++ application which will initially >run on ORACLE (and subsequently may run on Sybase and >Informix). In this application, there will be scenarios >under which a database transaction may be open for a few >days. > >We are told that under ORACLE, having a transaction open >for long durations (as in days) does not present any >significant impact on performance and other database >resources. Is this correct? What about with Sybase and >Informix? Is there anyone who may wish to caution us on >any potential problems that such long lasting >transcations would present. I for one, thought that >there could be problems with tranaction log files. > >Thanks in advance > >--bill > Bill, Could you give more details on what type of transaction you're talking about. Specifically, is it an update transaction or read only? What do you mean by the transaction being active for days? If you mean the application is up for days that's one thing if you mean an individual user's transaction is active for days that's probably not good. If you'd like you can Email me and we can discuss it. Greg Flannery Database Administration Tennessee Valley Authority