For how many years have you been working
with physical servers that are starving your database of the memory
necessary to deploy important new performance features such as the Result
Cache, Memoptimize Pool, In-Memory Aggregation, In-Memory Column Store, and
Full Database Caching? Too long? Contact me to learn how to improve all
queries ... not just some queries.
Provides an interface to determine if the in-flight transaction on a now unavailable session committed or not, and if the last call on that session completed or not.
err_server_ahead: the server is ahead, so the transaction is an old transaction and must have already been committed.
err_client_ahead: the client is ahead of the server. This can only happen if the server has been flashbacked or the ltxid is corrupted. The outcome cannot be determined.
Owned by SYS with EXECUTE granted to the DBA role
Lets customer applications and third party application servers determine the transactional status of the last session when that session becomes unavailable
client_ltxid IN RAW, -- LTXID for JDBC, LogicalTransactionId for ODP.net
committed OUT BOOLEAN,
user_call_completed OUT BOOLEAN);