Oracle DBMS_APP_CONT
Version 12.2.0.1

General Information
Library Note Morgan's Library Page Header
"I spent my entire adult life looking out for the well-being, the training, the equipping of the troops for whom I was responsible. I will not be lectured about what our military needs by a five-deferment draft dodger,"
~ Sen. Tammy Duckworth
Purpose 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.
AUTHID DEFINER
Constants
Name Data Type Value
COMMITTED NUMBER(1) 2
NOT_COMMITTED NUMBER(1) 1
Dependencies
DBMS_APP_CONT_LIB    
Documented Yes
Exceptions
Error Code Reason
-14950 err_server_ahead: the server is ahead, so the transaction is an old transaction and must have already been committed.
-14951 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.
-14952 err_general_failure
First Available 12.1.0
Security Model Owned by SYS with EXECUTE granted to the DBA role
Source {ORACLE_HOME}/rdbms/admin/dbmsappcont.sql
 
GET_LTXID_OUTCOME
Lets customer applications and third party application servers determine the transactional status of the last session when that session becomes unavailable dbms_app_cont.get_ltxid_outcome(
client_ltxid        IN  RAW, -- LTXID for JDBC, LogicalTransactionId for ODP.net
committed           OUT BOOLEAN,
user_call_completed OUT BOOLEAN);
TBD

Related Topics
AS_REPLAY
DBMS_APP_CONT_PRVT
DBMS_WORKLOAD_CAPTURE
DBMS_WORKLOAD_REPLAY
DBMS_WRR_INTERNAL
Packages
What's New In 12cR1
What's New In 12cR2

Morgan's Library Page Footer
This site is maintained by Dan Morgan. Last Updated: This site is protected by copyright and trademark laws under U.S. and International law. © 1998-2017 Daniel A. Morgan All Rights Reserved