Hi there,
just got a few problems with the transaction rollback functionality of openege 10.1A.
1. discovered problem complete transactions disappeard or have not been performed to the database - there hasn't been any applycation crash at this time. --> for that i tried the -nosavepoint qualifier
2. discovered problem (occures with and without -nosavepoint).
user interface crashes and the work eg. of an hour or two gets rolledback.
Fact is the user is working the whole time with the same window calling different subroutines (dynamic buttons). Tried with exclusive locks instead of shared locks - no change (only the number of locks was cut down, 'cause it seemed to me that some shared-locks have not been released after updating even with releasing the table).
yesterday i've lost 100+ entries (also in the audit-table) and i don't know how to prevent the application to do so......
any idea?`
thanx cugar
just got a few problems with the transaction rollback functionality of openege 10.1A.
1. discovered problem complete transactions disappeard or have not been performed to the database - there hasn't been any applycation crash at this time. --> for that i tried the -nosavepoint qualifier
2. discovered problem (occures with and without -nosavepoint).
user interface crashes and the work eg. of an hour or two gets rolledback.
Fact is the user is working the whole time with the same window calling different subroutines (dynamic buttons). Tried with exclusive locks instead of shared locks - no change (only the number of locks was cut down, 'cause it seemed to me that some shared-locks have not been released after updating even with releasing the table).
yesterday i've lost 100+ entries (also in the audit-table) and i don't know how to prevent the application to do so......
any idea?`
thanx cugar