Kbase 21415: FOR EACH EXCLUSIVE & Transaction Log Considerations in V9.1C
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
16/10/2008 |
|
Status: Verified
GOAL:
FOR EACH EXCLUSIVE & Transaction Log Considerations in V9.1C
FACT(s) (Environment):
Progress 9.1X
CAUSE:
Why from the following code, you won't see a transaction written in the Transaction Log (_trans, VST), or with promon.
FOR EACH CUSTOMER EXCLUSIVE-LOCK:
MESSAGE TRANSACTION.
UPDATE CUSTOMER.NAME.
PAUSE.
END.
FIX:
This is because transactions are buffered at several levels to optimize performance.
The 4GL does not tell the Database right away that it wants a transaction. It waits until it has to tell the database. The database also waits until it has to before actually writing a transaction log entry to record the fact that a transaction is starting.
None of this matters to the application. As far as it is concerned, it has a transaction active.
NOTE: To activate a transaction doesn't mean that a transaction has started.