Search Results get_context




Overview
Explore in AI Chat

Overview

SYS.DBMS_LOGSTDBY_CONTEXT is a server-side PL/SQL package that maintains session-level name/value context pairs used by Oracle Data Guard and the SQL Apply (logical standby) engine. In the Oracle E-Business Suite 12.1.1 and 12.2.2 environments, this package is an Oracle database kernel object owned by SYS, not an EBS application object. The ETRM registry classifies it under the API category OTHER, reflecting that it is a database-supplied utility rather than an EBS business API.

Its business function in an EBS context is diagnostic and operational rather than functional. When a logical standby database is configured as part of a disaster-recovery or reporting-offload architecture for an EBS instance, the SQL Apply engine references session context to determine how DML on EBS application tables should be applied. Administrators and support engineers use this package to inspect, set, or remove that context in order to influence apply behavior, isolate apply problems, or gather evidence during tuning of the standby.

Key Procedures and Functions

The ETRM metadata documents four procedures in the package specification:

  • SET_CONTEXT — establishes or updates a named context value for the current session. It is used to define a context entry that the SQL Apply or calling session will subsequently read.
  • GET_CONTEXT — retrieves the value associated with a supplied context name, returning it through an output parameter. This is the primary inspection routine for verifying what context is currently in effect.
  • CLEAR_CONTEXT — removes a single named context entry, allowing targeted cleanup without disturbing other entries.
  • CLEAR_ALL_CONTEXT — removes every context entry in the current session. This is the routine most commonly sought by users searching for clear_all_context, and it is the broadest reset operation in the package.

The specification declares no functions and no additional overloads; the interface is limited to these four procedures.

Tables Accessed

The ETRM metadata records no tables referenced through APPS synonyms for this package. This is consistent with its design: the context values are held in session memory (PL/SQL package state and session context), not persisted to application tables. Because no EBS schema objects are read or written, the package does not interact with the APPS tablespace or with any EBS business entity. Any internal dictionary access is performed as the SYS owner and falls outside the ETRM application data model.

Usage Notes

The package is not invoked by standard EBS forms, concurrent programs, or workflow. It is referenced by zero other packages according to the ETRM dependency record, which indicates no EBS application code depends on it. Invocation therefore occurs through direct SQL*Plus or DBA sessions, typically in these circumstances:

  • During Data Guard logical standby configuration and validation, when an administrator needs to confirm the active apply context.
  • During troubleshooting of apply errors or unexpected DML behavior on a standby that supports an EBS environment.
  • In controlled test scenarios, where context is set, exercised, and then removed with CLEAR_CONTEXT or CLEAR_ALL_CONTEXT to restore a clean session state.

Because context is session-scoped, CLEAR_ALL_CONTEXT affects only the calling session and carries no database-wide impact. Custom code should avoid reliance on this package for application logic; it is intended for database administration and Data Guard operational use, and Oracle may change its behavior between database releases independently of EBS patch levels.