Search Results lock_infrastructure

Overview

AD_FILE_UTIL is a utility package owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its primary business function is to support the Oracle Applications file system infrastructure used during patching, snapshot preseeding, and checkfile processing. The package header carries the AUTHID CURRENT_USER directive, meaning that all unqualified object references resolve against the invoking schema rather than the definer schema. This is significant because the package is designed to be called from AD administration scripts, patching utilities, and concurrent processing routines that operate under the APPLSYS schema.

At its core, AD_FILE_UTIL manages the staging and loading of file-system metadata into the AD dictionary tables. It provides the serialization mechanism that allows multiple concurrent scripts to safely share the AD_CHECK_FILE_TEMP staging table, and it supplies the loaders that move staged rows into the persistent AD_FILES, AD_FILE_VERSIONS, and related repositories. In this sense, the package is part of the foundational plumbing that lets AutoPatch, adpatch, and the snapshot preseeding processes reconcile the physical file system against the database records of the Applications file hierarchy.

Key Procedures and Functions

The package exposes eighteen documented procedures and functions. The most prominent are:

• LOCK_INFRASTRUCTURE — Acquires the infrastructure-level User Lock that serializes access to the shared temporary structures used across file-loading scripts.
• UNLOCK_INFRASTRUCTURE — Releases the User Lock acquired by LOCK_INFRASTRUCTURE when all batches have completed processing. This is the procedure most frequently referenced in searches, since a stuck infrastructure lock is a common source of patching blockages.
• LOCK_AND_EMPTY_TEMP_TABLE — Serializes access to AD_CHECK_FILE_TEMP using a DBMS_LOCK session-level User Lock and empties the table so that each batch begins from a clean state.
• LOAD_FILE_INFO — Imports file information from AD_CHECK_FILE_TEMP into AD_FILES, creating only rows that do not already exist.
• LOAD_FILE_VERSION_INFO, LOAD_CHECKFILE_INFO, LOAD_PATCH_ONSITE_VERS_INFO, LOAD_SNAPSHOT_FILE_INFO, LOAD_PRESEEDED_BUGFIXES, LOAD_PATCH_HIST_ACTION, LOAD_PREPMODE_CHECKFILE_INFO, and LOAD_SNPST_FILE_SERVER_INFO — Specialised loaders that stage and persist snapshot, bugfix, patch-history, and checkfile data into their respective dictionary tables.
• UPDATE_TIMESTAMP — Refreshes the timestamp columns on the affected dictionary rows.
• CREATE_GLOBAL_VIEW — Establishes a global view over the file metadata for downstream consumers.
• POPULATE_SNAPSHOT_FILES_TEMP and POPULATE_SNAPSHOT_BUGS_TEMP — Seed the temporary snapshot staging tables prior to loading.
• CLN_PREPMODE_CHECKFILE_INFO — Cleans up preparation-mode checkfile data after processing.

Tables Accessed

AD_FILE_UTIL reads and writes a specific set of AD dictionary tables, all accessed through APPS synonyms:

• AD_CHECK_FILE_TEMP — The central staging table for file and bugfix rows prior to loading; serialized and emptied by LOCK_AND_EMPTY_TEMP_TABLE.
• AD_FILES, AD_FILES_S, AD_FILE_VERSIONS, AD_FILE_VERSIONS_S — Persistent repositories of registered files and their version history.
• AD_CHECK_FILES, AD_CHECK_FILES_S, AD_CHECK_FILE_HISTORY — Checkfile registration and history tables.
• AD_BUGS, AD_BUGS_S — Bugfix registrations loaded via the preseeding procedures.
• AD_APPL_TOPS, AD_APPL_TOPS_S — Application top definitions used to resolve file paths.
• AD_PATCH_COMMON_ACTIONS, AD_PATCH_COMMON_ACTIONS_S, AD_PATCH_HIST_TEMP — Patch action and patch history staging structures.

Usage Notes

AD_FILE_UTIL is not intended to be invoked interactively from Oracle Forms. It is called from AD administration scripts, AutoPatch, snapshot preseeding routines, and concurrent programs that need to reconcile the physical Applications file system against the AD dictionary. The documented usage pattern requires each caller to call LOCK_AND_EMPTY_TEMP_TABLE, insert rows into AD_CHECK_FILE_TEMP, gather statistics on that table, invoke the relevant loader, and commit — repeating the cycle for each batch before finally calling UNLOCK_INFRASTRUCTURE. When a patching session aborts unexpectedly, the residual infrastructure lock can be released by invoking UNLOCK_INFRASTRUCTURE explicitly, which is why the procedure is commonly sought by DBAs and EBS technicians. Custom code should treat the package as an internal utility and avoid calling it outside established AD patch and snapshot workflows.