Results for “in_process_flag”

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

Overview

AD_WORKING_RES_LOCKS is a metadata table owned by the APPLSYS schema in Oracle E-Business Suite, classified under the AD – Applications DBA product. As its name implies, the table stores active resource locks acquired by AD utilities such as adpatch, adadmin, AutoConfig, and related concurrent programs during patching and maintenance operations. The table acts as a coordination mechanism that prevents two AD sessions from simultaneously modifying the same resource within the same context, thereby protecting the integrity of the APPL_TOP file system and the underlying database objects.

From a Data Vault modeling perspective, the ETRM metadata classifies this object heuristically as standalone. This suggests the table functions as an independent entity rather than as a classic hub, link, or satellite, though its composite unique key and single foreign key to AD_APPL_TOPS imply it could conceptually be modeled as a link between an AD session and a resource. The single documented foreign key, AD_WORKING_RES_LOCKS.APPL_TOP_ID → AD_APPL_TOPS, ties each lock record to a specific application tier.

Key Information Stored

The table contains 14 documented columns in ETRM 12.2.2. The most significant business-key candidates are defined by the unique index AD_WORKING_RES_LOCKS_U1, which spans SESSION_ID, RESOURCE_CODE, CONTEXT, APPL_TOP_ID, LANGUAGE, EXTRA_CONTEXT1, EXTRA_CONTEXT2, EXTRA_CONTEXT3, and IN_PROCESS_FLAG. This composite key uniquely identifies a lock held by a particular session against a particular resource.

• SESSION_ID – Identifier of the AD session holding the lock.
• RESOURCE_CODE – Logical name of the locked resource (for example, a patching resource or worker).
• CONTEXT – Contextual qualifier narrowing the scope of the lock.
• APPL_TOP_ID – Foreign key to AD_APPL_TOPS identifying the application tier.
• LOCK_MODE – Mode of the lock (shared, exclusive, and so on).
• LANGUAGE – Language code participating in the unique key.
• IN_PROCESS_FLAG – Flag indicating whether the lock is currently being processed.
• SESSION_STATUS – Current status of the owning session.
• SESSION_PRIORITY – Priority used for lock arbitration.
• DATE_REQUESTED – Timestamp when the lock was requested.
• DATE_ACQUIRED – Timestamp when the lock was actually granted.
• EXTRA_CONTEXT1, EXTRA_CONTEXT2, EXTRA_CONTEXT3 – Additional contextual discriminators completing the unique key.

No separate surrogate primary key column is documented; the unique index serves as the business-key candidate.

Common Use Cases and Queries

DBAs and AD utilities consult this table to detect stale or orphaned locks that block patching. A typical diagnostic query lists active locks for a session or resource:

• SELECT session_id, resource_code, context, lock_mode, date_requested, date_acquired FROM ad_working_res_locks WHERE in_process_flag = 'Y';
• SELECT * FROM ad_working_res_locks WHERE resource_code = :resource AND appl_top_id = :appltop;
• Joining to AD_APPL_TOPS to identify the application tier hosting a lock.
• Reporting lock contention by session priority and acquisition delay.

These patterns help administrators identify blocking sessions, verify that adpatch has released resources, and confirm that no parallel AD worker is holding a conflicting lock before retrying a failed operation.

Related Objects

• AD_APPL_TOPS – Referenced via APPL_TOP_ID; identifies the application tier.
• AD_WORKING_RES_LOCKS_U1 – Unique index enforcing the business key.
• AD_SESSIONS and AD session-related views – Provide session context for SESSION_ID.
• AD_PATCH_DRIVER_* and adpatch log tables – Correlate locks with running patch drivers.
• FND_CONCURRENT_REQUESTS – Links AD utility runs to concurrent program submissions.