Which has the higher priority in your organization: Deploying a new database or securing the ones you already have?
Looking for a website, and resources, dedicated solely to securing Oracle databases? Check out DBSecWorx.
Used to provide 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.
All of its functionality with the exception of a single object was split out into a new package named DBMS_APP_CONT_ADMIN and the documentation was partially update to reflect the change but the required docs for DBMS_APP_CONT_ADMIN are missing.
Will be opening an SR later this evening. This looks like more of the work of Oracle's Executive VP of Product Renaming.
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);