G
gus
Guest
there are three possible transaction start situations (v9 and later): 0) when the transaction starts in the (4GL) client. But here it is delayed as long as possible so the database is not told about it right away even though the application may be executing inside a "do transaction" block. the datbase does not know the clinet wants a transaction, or the transaction may be started in one connected database and not in another. promon does notshow a transaction for the client. 1) the 4GL has told the database it wants to start a transaction but the transaction start is being postponed until the clinet performs a database operation that makes a change to the database. the database knows about the transaction and is lying to the client about it. promon show a transactionstate of "Begin" and is lying to you. 2) the transaction bein note has been written o the transaction log in the database. promon shows the transaction as "Active". of the three, the only one that matters is the last.
Continue reading...
Continue reading...