Oracle | DBMS_APP

Oracle DBMS_APP_CONT Version 26ai

General Information

Library Note

Morgan's Library Page Header

The best Oracle News for FY2026

Oracle Database 26ai will be available on generic Linux platforms in January and soon on AIX and Windows

Purpose Used to provide an interface to determine if the in-flight transaction on a now unavailable session committed and if the last call on that session successfully completed.

AUTHID DEFINER

Constants

Name	Data Type	Value
General
NOT_COMMITTED	NUMBER(1)	1
COMMITTED	NUMBER(1)	2
Target Effects
SIDE_EFFECTS	NUMBER	1
AUTONOMOUS_TRANSACTIONS	NUMBER	2
DATABASE_LINKS	NUMBER	4
PL/SQL Scope
SCOPE_CURRENT	NUMBER	1
SCOPE_PARENT	NUMBER	2

Dependencies

DBMS_APP_CONT_LIB

DBMS_STANDARD

Documented Yes: Packages and Types Reference

Exceptions

Error Code	Reason
ORA-14950	err_server_ahead: the server is ahead, so the transaction is an old transaction and must have already been committed.
ORA-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.
ORA-14952	err_general_failure

First Available 12.1

Pragma PRAGMA SUPPLEMENTAL_LOG_DATA(default, NONE);

Security Model Owned by SYS with EXECUTE granted to the DBA role

Source {ORACLE_HOME}/rdbms/admin/dbmsappcont.sql

Subprograms

APPLY_REPLAY_RULE	GET_REPLAY_RULES	RESET_REPLAY_RULES
GET_LTXID_OUTCOME

APPLY_REPLAY_RULE (new 23ai)

A replay rule specifies if one or more of the above rule targets are replayable or not replayable dbms_app_cont.apply_replay_rule( replayable IN BOOLEAN, targets IN BINARY_INTEGER, scope IN BINARY_INTEGER DEFAULT SCOPE_CURRENT);

TBD

GET_LTXID_OUTCOME

Allows customer applications and third party application servers to 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

GET_REPLAY_RULES (new 23ai)

Returns replay rules. Use to test if any rule target is replayable with bitand function dbms_app_cont.get_replay_rules( replayable IN BOOLEAN, scope IN BINARY_INTEGER DEFAULT SCOPE_CURRENT) RETURN BINARY_INTEGER;

TBD

RESET_REPLAY_RULES (new 23ai)

Resets replay rules by clearing locally defined rules in the desired scope and restore them to what's inherited from the parent scope, or the service if it doesn't have a parent scope dbms_app_cont.reset_replay_rules( targets IN BINARY_INTEGER DEFAULT NULL, scope IN BINARY_INTEGER DEFAULT SCOPE_CURRENT);

TBD