Results for “extra_context2”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

AD_PLANNED_RES_LOCKS is a table owned by the APPLSYS schema within the Applications DBA (AD) product of Oracle E-Business Suite. Per the ETRM metadata, its documented purpose is to store locks to be required by an AD Utility. In practical terms, the table functions as a planning and coordination mechanism for the AD utilities — programs such as AutoPatch (adpatch), AD Administration (adadmin), and related maintenance drivers — that must serialize access to shared resources while they execute. Before an AD utility acquires a resource lock, it records the intent in AD_PLANNED_RES_LOCKS, allowing the tool to detect conflicts, avoid deadlocks, and coordinate parallel workers against the same resource.

From a Data Vault modeling perspective, the heuristic classification mined from the foreign key structure is standalone — no parent hub relationships beyond the APPL_TOP_ID reference are implied. This is a reasonable modeling suggestion: the table behaves more like a transient operational/work table than a durable master or transactional entity, and its rows are meaningful only for the duration of an AD utility session.

Key Information Stored

The documented physical schema for 12.2.2 contains twelve columns. The most significant are:

• SESSION_ID — identifies the AD utility session that is planning or holding the lock; used to group and isolate concurrent runs.
• STAGE_CODE — the AD processing stage during which the lock is planned, allowing stage-scoped coordination.
• RESOURCE_CODE — the logical resource (file, tablespace, worker set, or object) against which the lock is planned.
• CONTEXT — the resolution context for the resource code, typically identifying the specific instance, application, or path affected.
• LOCK_MODE — the intended lock mode (for example, shared versus exclusive), governing compatibility with other planned locks.
• APPL_TOP_ID — foreign key to AD_APPL_TOPS, tying the planned lock to a specific APPL_TOP in multi-tier or multi-APPL_TOP installations.
• LANGUAGE — language context for the lock, relevant where translated or NLS-specific resources are involved.
• ACTION_FLAG — indicates the action to be taken (acquire, release, or similar) for the planned lock.
• DONE_FLAG — marks whether the planned lock operation has completed.
• EXTRA_CONTEXT1, EXTRA_CONTEXT2, EXTRA_CONTEXT3 — three overflow context columns providing additional qualifiers where the primary CONTEXT is insufficient.

The unique index AD_PLANNED_RES_LOCKS_U1 spans SESSION_ID, STAGE_CODE, RESOURCE_CODE, CONTEXT, APPL_TOP_ID, LANGUAGE, EXTRA_CONTEXT1, EXTRA_CONTEXT2, EXTRA_CONTEXT3, and ACTION_FLAG. This composite defines the business-key candidate: a given session may plan only one lock entry per stage, resource, context, APPL_TOP, language, extra context combination, and action. The table carries no separately documented surrogate primary-key column in the metadata, so the unique index effectively serves as the identifier for each planned lock row.

Common Use Cases and Queries

Primary use cases are diagnostic and operational. DBAs troubleshooting a stalled or conflicting AD patch run query this table to identify which session planned which locks and whether those locks completed. Representative patterns include:

• Listing outstanding planned locks for an active session: SELECT stage_code, resource_code, context, lock_mode, done_flag FROM ad_planned_res_locks WHERE session_id = :sid AND done_flag = 'N';
• Detecting resource contention across sessions: SELECT resource_code, context, COUNT(*) FROM ad_planned_res_locks GROUP BY resource_code, context HAVING COUNT(*) > 1;
• Scoping locks to a specific APPL_TOP: join on appl_top_id to determine which tier's resources are affected.
• Post-run auditing of which stages completed, using done_flag and action_flag to confirm orderly lock release.

Reporting against this table is typically ad hoc and short-lived, since rows are transient by design.

Related Objects

• AD_APPL_TOPS — referenced by the APPL_TOP_ID foreign key; the primary documented parent of this table.
• AD_SESSIONS / session tracking tables — supply the SESSION_ID used for correlation with an AD utility run.
• AD_WORKER_LOCKS / worker coordination tables — companion structures used by parallel AD utilities.
• FND_APPL_TOP — related APPL_TOP registry view used in many AD joins.
• AD Utilities APIs (adpatch, adadmin, adctrl) — the runtime consumers that populate and resolve planned locks.