Search Results get_snapshot_type

Overview

AD_FILE_SYS_SNAPSHOTS_PKG is an Oracle Applications (APPS) schema PL/SQL package that supports the file system snapshot framework used by Oracle E-Business Suite's patching and file management infrastructure. In Oracle EBS 12.1.1 and 12.2.2, the AD (Applications DBA) product maintains snapshots of application tier file systems and database object states to detect and manage changes introduced by patches, upgrades, and configuration updates. This package provides the procedural logic that allows the patching utilities to determine which snapshot type is in effect, decide whether snapshot maintenance is currently permitted, materialize and refresh database views that expose the "current" state of the file system relative to a snapshot, backfill patch history records where snapshot data is incomplete, and update release naming information associated with a snapshot.

Because EBS patching depends on knowing precisely which files and versions exist at a given point, this package acts as a support utility rather than an end-user facing API. It is closely tied to the AutoPatch processing model and the snapshot comparison logic that drives file synchronization and patch application decisions.

Key Procedures and Functions

• GET_SNAPSHOT_TYPE — Determines and returns the snapshot type in context, allowing callers to branch behaviour based on whether the snapshot represents a file system, database, or combined state.
• SNAPSHOT_MAINT_ALLOWED — Evaluates whether snapshot maintenance operations may proceed, typically by checking system conditions or configuration prerequisites before permitting snapshot updates.
• UPDATE_CURRENT_VIEW — Refreshes the database view that represents the current snapshot view, keeping the exposed data consistent with underlying snapshot tables.
• INSTANTIATE_CURRENT_VIEW — Creates or materializes the current snapshot view when it does not already exist, establishing the view object used by subsequent queries.
• BACKFILL_BUGS_FROM_PATCH_HIST — Populates snapshot bug-fix records from historical patch history data, reconciling missing or migrated entries in the snapshot bug mapping.
• UPDATE_REL_NAME — Updates the release name associated with a snapshot, keeping release identification consistent for reporting and comparison purposes.

The package also exposes additional supporting procedures (seven documented in total) that operate in the same snapshot maintenance domain.

Tables Accessed

The package reads and writes across the AD snapshot and patch data model, including:

• AD_APPL_TOPS, AD_APPL_TOPS_S — Application tier top definitions used to resolve file system locations. The _S variant stores snapshot-related copies.
• AD_FILES, AD_FILES_S, AD_FILE_VERSIONS — File inventory and file version data central to snapshot comparison.
• AD_SNAPSHOTS, AD_SNAPSHOTS_S, AD_SNAPSHOT_BUGFIXES — The core snapshot headers, snapshot copies, and the mapping of snapshots to bug fixes.
• AD_PATCH_RUNS, AD_PATCH_RUN_BUGS, AD_PATCH_RUN_BUG_ACTIONS, AD_PATCH_COMMON_ACTIONS, AD_PATCH_DRIVERS, AD_PATCH_HIST_SNAPS_TEMP — Patch execution and history tables, including the temporary snapshot history staging table used during backfill.
• AD_RELEASES — Release definitions leveraged when updating release names.

Usage Notes

AD_FILE_SYS_SNAPSHOTS_PKG is referenced by AD_PATCH and AD_PATCH_HIST_MIGR_PKG, and is recursively referenced by itself, indicating use across patching, patch history migration, and snapshot maintenance flows. It is typically invoked indirectly by AutoPatch and related AD utilities rather than through a standard Oracle Forms interface or a user-facing concurrent program. Custom code should treat it as an internal support package: it is owned by APPS and classified under the ETRM as OTHER, meaning it is not a published, supported API. Developers integrating with snapshot logic should call documented AutoPatch entry points instead of invoking these procedures directly, and any reliance on them should be validated against the specific EBS release (12.1.1 or 12.2.2), since the underlying table structures and snapshot behaviour differ between those releases.